Skip to content
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

Deep object's don't support nullable.Nullable or more complex types like uuid.UUID #44

Open
j-waters opened this issue Jun 7, 2024 · 0 comments · May be fixed by #45
Open

Deep object's don't support nullable.Nullable or more complex types like uuid.UUID #44

j-waters opened this issue Jun 7, 2024 · 0 comments · May be fixed by #45

Comments

@j-waters
Copy link

j-waters commented Jun 7, 2024

If you set nullable-type: true in your oapi-codegen config file and then use nullable: true in a field in a deep object, the deep object unmarshalling breaks. That's because nullable.Nullable is implemented as a map, and there is no special handling here.

Similarly, if you use format: uuid in a string field in a deep object, you'll get an error like this:

"Invalid format for parameter filter: error assigning value to destination: error assigning field [entity]: unhandled type: uuid.UUID"

Which I'm fairly sure comes from here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant