Get-Only Swagger UI - #162
Merged
Merged
Conversation
sgmv
previously approved these changes
May 21, 2026
sgmv
approved these changes
May 21, 2026
This branch was previously deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Serves Swagger UI at /swagger/any using gin-swagger
Dynamically filters openapi.yaml to expose only GET methods
Strips /auth/ paths, security block, securitySchemes, and Token* schemas
Removes RBAC-only fields (creator, contact_email, version) from response schemas
Overrides servers.url from the incoming request host (supports X-Forwarded-Proto)
Fixes openapi.yaml: realistic date examples, limit enum [10, 20, 50]
Limitations:
Swagger UI operates without authentication — all requests are anonymous
Only GET endpoints are visible; no mutation operations exposed