Merge upstream from py-swagger-ui #32
Merged
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
This was referenced Oct 25, 2023
Closed
Closed
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.
This PR contains the changes made to py-swagger-ui. I just added a commit to rename everything back to
swagger_ui_bundle.Note that this does contain some breaking changes, since we dropped version 2 and 3 in favor of version 4, and changed the import variables accordingly. I don't think this is an issue though, as I would bump the version to 1.1.0 to match the
py-swagger-uiversion. Theswagger-ui-bundleversion has had an upper limit in Connexion since 2.8.0, and for older versions it's easy to fix by pinningswagger-ui-bundle.