-
Notifications
You must be signed in to change notification settings - Fork 87
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
Support custom format
types.
#1335
Comments
It would be nice. This feature was requested before. I think it is better to configure it via extension |
Thanks for getting back to me on this @tdakkota! Both oapi-codegen and go-swagger use different formats though: oapi-codegen x-go-type: googleuuid.UUID
x-go-type-import:
path: github.com/google/uuid
name: googleuuid go-swagger x-go-type:
import:
package: github.com/google/uuid
alias: googleuuid
type: UUID I personally still prefer the idea of writing a single field e.g. x-go-type: github.com/google/uuid.UUID We could also automatically alias it if there's a clash between package names. What's your preference? |
Me too. |
Any news on this issue, it would be nice to see this implemented? |
It would be really cool. |
Description
I'd like to propose adding support for custom
format
types. These could come from the configuration. Maybe something like the following example:This would result in a field with
format: decimal
to be of the typedecimal.Decimal
from the packagegithub.com/shopspring/decimal
.Alternatively, we could implement this as an extension e.g.
We can implement some checks to ensure the package is importable, as well as checking that the type implements one of the following interfaces:
Based on which of the interfaces it implements we can use a different template for encoding and decoding the value.
I'm happy to implement this feature, just wanted to first check if such a feature would be accepted and get alignment on the way it's configured.
The text was updated successfully, but these errors were encountered: