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

[Question] Why is uint32 mapped to {"integer", "int64", 0.} #513

Open
manusa opened this issue Oct 29, 2024 · 0 comments
Open

[Question] Why is uint32 mapped to {"integer", "int64", 0.} #513

manusa opened this issue Oct 29, 2024 · 0 comments

Comments

@manusa
Copy link

manusa commented Oct 29, 2024

Description

uint32 is currently mapped to OpenAPI numeric integertype which seems OK, but with a format of int64.
Is there any reason for this? or is it a typo?

The mapping is located here:

"uint32": {"integer", "int64", 0.},

This is problematic because at the moment, for example, fields representing server ports are typed as int64 which map them to misleading types such as Long in Java.

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

No branches or pull requests

1 participant