-
Notifications
You must be signed in to change notification settings - Fork 183
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
fix(java): Line up protobuf type handling with our other generators #6322
Conversation
@@ -183,7 +183,7 @@ public String visitLong() { | |||
|
|||
@Override | |||
public String visitUint() { | |||
return "Long"; | |||
return "Integer"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we should name this distinct even though it still maps to an int
. That way if a user has an undiscriminated union with both there's no conflict. Otherwise the following type would have two things named with Integer
:
types:
Number:
discriminated: false
union:
- uint
- integer
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah ignore me, I was thinking this would be used in the union generator, but this detail likely isn't relevant for Java!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
We were using longs for uints, when we should have been using ints