Support optional API version segment in path #91
+217
−1
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-version-path
branch
from
5a360ad
to
2abbb9e
Compare
stempler
force-pushed
the
pr/api-version-path
branch
from
038fc90
to
4e4597c
Compare
stempler
force-pushed
the
pr/api-version-path
branch
from
4e4597c
to
aef07a7
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_path_segmentcan be used to enable the behavior that:v1for major version1, example path/datasets/streets/v1/collections), paths that don't include this version segment still work as beforeThe version segment was added at this place in the path, because for each dataset a separate API with its own API definition is provided by deegree OAF.
Solves #73