feat(rest): add config option to disable API Explorer redirects #2016
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
7 tasks
raymondfeng
reviewed
Nov 12, 2018
bajtos
force-pushed
the
feat/disable-swagger-redirect
branch
from
cef166c to
96fe6a1
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.
To allow users to mount self-hosted API Explorer at
/explorer, we need to allow them to disable the redirect pointing/explorerto the externally hosted swagger-ui instance.In this pull request, I am modifying the REST component to allow the config option
rest.apiExplorerto be configured tofalse, thus disabling redirects.See also #1664, #1976, #1960 and #559.
Checklist
npm testpasses on your machinepackages/cliwere updatedexamples/*were updated