feat(swagger): JSON and YAML document endpoints customizable #2046
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?
Right now the swagger json and yam are deployed in
${finalPath}-json
and${finalPath}-yaml
, without possibility of customization:Issue Number: #1968
What is the new behavior?
Added the options
jsonDocumentUrl
andyamlDocumentUrl
in the interfaceSwaggerCustomOptions
If the option value is present, json and/or yaml documents are served in the specified url.
Furthermore, if
globalPrefix
is specified in the nest options, it's used as prefix for the custom urls.Does this PR introduce a breaking change?
Other information