-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ReDoc uses unmodifiable spec path #226
Labels
Comments
This still seems to be an issue. |
Studying this issue report, I gather that:
|
fredbi
added a commit
to fredbi/runtime
that referenced
this issue
Dec 11, 2023
- refactored UI middleware * factorized chore middleware to remove duplicated code * factorized UI middleware options: to avoid breaking changes in the options types, there is a decode/encode to a common structure * added more options: * allows to fully customize the UI template * added more unit tests - Spec middleware: added support for optional SpecOption argument * allows to serve the spec from a custom path / document name - serving with or without trailing "/" (cf. issue go-openapi#238) * replaced path.Join() by path.Clean(), which is the intended behavior (i.e. serve the path, irrespective of the presence of a trailing slash) * generalized this behavior to all UI and Spec middleware, not just swaggerUI - API Context: * exposed middleware to serve RapiDoc UI * allowed new UIOption (...UIOption) to the APIHandler, etc middleware * coordinated UI / Spec middleware to be consistent when non-default path/document URL is served * fixes go-openapi#192 * fixes go-openapi#226 Signed-off-by: Frederic BIDON <[email protected]>
fredbi
added a commit
to fredbi/runtime
that referenced
this issue
Dec 11, 2023
- refactored UI middleware * factorized chore middleware to remove duplicated code * factorized UI middleware options: to avoid breaking changes in the options types, there is a decode/encode to a common structure * added more options: * allows to fully customize the UI template * added more unit tests - Spec middleware: added support for optional SpecOption argument * allows to serve the spec from a custom path / document name - serving with or without trailing "/" (cf. issue go-openapi#238) * replaced path.Join() by path.Clean(), which is the intended behavior (i.e. serve the path, irrespective of the presence of a trailing slash) * generalized this behavior to all UI and Spec middleware, not just swaggerUI - API Context: * exposed middleware to serve RapiDoc UI * allowed new UIOption (...UIOption) to the APIHandler, etc middleware * coordinated UI / Spec middleware to be consistent when non-default path/document URL is served * fixes go-openapi#192 * fixes go-openapi#226 Signed-off-by: Frederic BIDON <[email protected]>
fredbi
added a commit
that referenced
this issue
Dec 12, 2023
- refactored UI middleware * factorized chore middleware to remove duplicated code * factorized UI middleware options: to avoid breaking changes in the options types, there is a decode/encode to a common structure * added more options: * allows to fully customize the UI template * added more unit tests - Spec middleware: added support for optional SpecOption argument * allows to serve the spec from a custom path / document name - serving with or without trailing "/" (cf. issue #238) * replaced path.Join() by path.Clean(), which is the intended behavior (i.e. serve the path, irrespective of the presence of a trailing slash) * generalized this behavior to all UI and Spec middleware, not just swaggerUI - API Context: * exposed middleware to serve RapiDoc UI * allowed new UIOption (...UIOption) to the APIHandler, etc middleware * coordinated UI / Spec middleware to be consistent when non-default path/document URL is served * fixes #192 * fixes #226 Signed-off-by: Frederic BIDON <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that when ReDoc is used, the OpenAPI 2.0/Swagger spec is defaulted to "/swagger.json" and ignores
basePath
while also providing no way to directly or indirectly set.SpecURL
in the Redoc template.In my situation, I'm hosting multiple separate APIs from the same listener. I can load Redoc from
myhost/api-type/api-sub-type/version/docs
but the rendered template always points tomyhost/swagger.json
.I could not find a way to provide an override, alter the value directly, or make the
basePath
from my OpenApi 2.0 spec be referenced in any way.Changes to
runtime
appear to be:RedocOpts
fieldSpecURL
to be a relative path: "./swagger.json" or "swagger.json" instead of "/swagger.json"RedocOpts
fieldSpecURL
to takeBasePath
into accountContext
If there is a different way to handle this or I am missing something please let me know!
The text was updated successfully, but these errors were encountered: