fix(): make swaggerUrl option work #1924
Closed
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
micalevisk
approved these changes
May 12, 2022
Tony133
approved these changes
May 13, 2022
mamane19
approved these changes
Aug 18, 2022
| @@ -78,7 +78,8 @@ export class SwaggerModule { | |||
| app.use(path, swaggerUi.serveFiles(document, options)); | |||
|
|
|||
| httpAdapter.get(path, (req, res) => res.send(swaggerHtml)); | |||
| httpAdapter.get(path + '-json', (req, res) => res.json(document)); | |||
| const swaggerUrl = options?.swaggerUrl ?? (path + '-json'); | |||
There was a problem hiding this comment.
I had this same issue earlier today, and I just manually tested this out. Works like charm!!
rubiin
approved these changes
May 7, 2023
|
Hi @omermecitoglu, as soon as you find some time you can resolve conflicts in this PR ? |
|
I think this issue has already been solved by #2273 |
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Currently it serves the swagger.json at /api-json path. But if you prefer to use root (/) as base path instead of api, your json url will become http://localhost:3000/-json
What is the new behavior?
With this change, swaggerUrl option lets developer to decide where to serve swagger.json
Does this PR introduce a breaking change?
Other information