-
-
Notifications
You must be signed in to change notification settings - Fork 920
hydra:view schema validation #967
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
1093815
to
c11ee29
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Should be merged in 2.0 (we'll do it).
@dunglas do you want me to rebase and/or retarget to 2.0 ? |
It will help yes. |
They proabbly never heard of semver :(
7f88a66
to
da80376
Compare
@dunglas rebased and retarget as requested |
Thanks @antograssiot |
@dunglas shouldn't this be added to master too? |
@antograssiot Why didn't you update composer.lock as well? |
@desmax probably because this file is not in the repo (nor should be IMO)... |
@antograssiot oh, my bad. sorry for disturbance |
* Fix Behatch namespace * Fix all hydra:view pattern check in json schema validation * Bump Behatch requirement
I found that the hydra:view schema validation pattern were not correctly checked in the testsuite. Any value would let the tests passing as the schema is malformed.
I've also updated the Behatch namespace as they changed it in 2.6 (call it deprecated) without providing a decent BC version.