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 fixes a problem I had with with the relative base path "/".
My swagger setup is the following:
http://localhost:8080/core/api-docs/
<- hosts the "main" api doc:http://localhost:8080/core/api-docs/api/2.0/report.json
<- hosts the actual api doc (for this example it's on the same server but actually it is be hosted elsewhere)Now, what I'd expect when i try out the "Fetch report data" endpoint, is for the URL to be the base path of the server the api documentation is on + the resource path.
What actually happens (before this pull request) is that I get a request for
http://localhost:8080/core/api-docs/api/2.0/report/
, clearly not what i want!With this fix, the url is
http://localhost:8080/api/2.0/report/
as expected.Hope you can understand this, I have to admit the different types of paths confuses me a bit but I'm pretty sure this is the way its supposed to work! :)