Dylan Hitt
Dylan Hitt
This is a great idea! We also appreciate your thoughtfulness when describing the feature. Im fairly certain you can just overwrite a route completely if needed, but I’m away from...
I guess the question is do we want the input for this override to be a Go type or do we want to allow the user to construct the type...
Just a thought for now. I think we'd want to continue our options pattern. Maybe a `OptionCustomSchema(whatever the schema input is)` In this case we'd want the caller to construct...
🤔 OH. I see now. I didn’t really look at your example close enough. I still think the option pattern can be used how you described, but I’ll look at...
I think this is more of issue on how we register the route. `http://localhost:8980/swagger/` We currently do this. ```go func (o *OpenAPIHandler) UIHandler(e *fuego.Engine) { GetEcho( e, o.Echo, e.OpenAPI.Config.SwaggerURL+"/", echo.WrapHandler(e.OpenAPI.Config.UIHandler(e.OpenAPI.Config.SpecURL)),...
I think we should close this, I looked through a few frameworks everyone seems to do this different. For example echo does it with middleware, gin does it with their...
Closing per comment above
So description really isn't a typo we support both go tags to parse into a openapi `example`. Removing `description` is pretty abrupt breaking change.
So to address the things for debate > 1. I've introduced new GoType - array, which is obviously OpenAPI type, not Go type. I would actually change this naming to...
@nrydanov any chance you have the time to address the comments above?