Construct the absolute resource basePath from relative one, using the Api basePath #59
Conversation
This file contains hidden or 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
…g the Api basePath
Contributor
|
This works, but note that most of the swagger tools will NOT work with relative base paths. |
fehguy
added a commit
that referenced
this pull request
Nov 4, 2013
…rom_relative Construct the absolute resource basePath from relative one, using the Api basePath
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This change allows using relative paths (like "api/v0", "v0" or simply "/") for the Resource's basePath value. In such cases the absolute resource's basePath is being constructed from relative one, using the runtime value of the parent api basePath.
Examples:
runtime api.basePath = http://myhost.com:8090/mywebapp/v0/api-docs
relative resource basePath = v0
=> absolute resource basePath = http://myhost.com:8090/mywebapp/v0
This also addresses and resolves the issue #52.