allow interceptors to be parsed as js functions UPDATED #38
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
To pass a function in as a parameter (i.e. requestInterceptor), you must ensure that in the code you write you define the function to have the same name as the parameter.
Dsolnik
changed the title
Updated README.md to show function parameters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 provides an alternative approach to adding swagger ui function parameters that supports older browsers.
I took the code from #35 written by @carlosreif and made some updates so that it would be able to support older browsers.
To pass a function parameter, the requester must be sure to name the function the same as the name of the parameter.
i.e.
get_swagger_ui_blueprint(prefix, url, config={'requestInterceptor':'function requestInterceptor(req){}'})