Fixes OGC API Features certification #37622
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pblottiere
added
Server
|
@pblottiere change https://github.com/qgis/QGIS/pull/37622/files#diff-449dc7aed73940e1295c380747db6ee5R379 and https://github.com/qgis/QGIS/pull/37622/files#diff-449dc7aed73940e1295c380747db6ee5R388 to "query" and the second issue will go away. |
|
@elpaso Thanks for the tip 👍 |
thank you for cleaning my mess :) |
pblottiere
force-pushed
the
fix_ogcapif_json
branch
3 times, most recently
from
e2a81f2
to
cf85ab6
Compare
pblottiere
force-pushed
the
fix_ogcapif_json
branch
from
cf85ab6
to
ce9e1ff
Compare
|
Azure build is failing but it's not related to this PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR is a follow-up to #37429 because OGC API Features certification tests are failing since the merge (cf http://test.qgis.org/ogc_cite/ogcapif/2020_07_06_05_00/report.html):
The first issue is fixed but I still have to take a look to others (according to https://apisecurity.io/encyclopedia/content/oasv3/oasconformance/structure/v3-validation-parameter-path-required.htm, a path parameter has to have its property 'required' set to 'true').