Support enabling API version response header #92
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
stempler
force-pushed
the
pr/api-response-header
branch
from
eb577ec to
f12846f
Compare
stempler
force-pushed
the
pr/api-response-header
branch
from
24615c9 to
c599d84
Compare
stempler
force-pushed
the
pr/api-response-header
branch
from
c599d84 to
9cdd8b2
Compare
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.
The system property
deegree.oaf.openapi.version_response_headercan be used to enable returning a response headerAPI-Versionwith the version of the implemented OGC API Features.The existing constant for the API version in the code has been changed to use a semantic version number including the patch version.
Solves #74