-
Notifications
You must be signed in to change notification settings - Fork 44
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
Code genertated from optional message field is mission optionality #475
Comments
Thanks! I'm on it. |
Hi, fixed with this PR: #476 After the PR's published, this setting can solve the issue: proto:
ts:
If you think this solution's ok, I'll merge and publish Thank you very much! |
I believe the unexpected results was because of Telescope consider the default value of (gogoproto.nullable) is false, which should be true. After this change, the default value will be true and the result: Proro:
will generate TS:
telescope 1.0.4 has been published with this fix |
Yeah, the Thank you for the fix! Looks good so far |
I have the following protobuf definition:
After upgrading to Telescope 0.109.0, the
instantiate_permission
got non-optional:However, this change is wrong as by default all message fields in protobuf should be optional. Only the ones annotated as non-optional should be non-toptional.
So the desired output for the above proto is:
This bug currently leads to "instantiate permission: type: empty" errors in cosmos/cosmjs#1484 because the field is set but empty and not unset as expected.
The text was updated successfully, but these errors were encountered: