feat: enable hosting custom Swagger UI #53
Merged
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
- Introduced a new SwaggerUI handler to serve the Swagger UI interface. - Updated app configuration to include Swagger UI parameters and routes. - Enhanced Settings class with new fields for Swagger UI configuration. - Ensured compatibility with OpenAPI spec endpoint when using Swagger UI.
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.
Given that the vanilla
stac-fastapi-pgstacapplication does not support specifyinginit_oauth(which makes sense, being that there's no authentication within the vanilla application), it does make sense to permit creating our own Swagger UI within this service.related to #15