-
-
Notifications
You must be signed in to change notification settings - Fork 285
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
sealed oneof option/annotation instead of special name #578
Comments
Yes, that should be fairly straightforward. Would you have time to put together a PR? There are initial instructions on getting started here: https://github.com/scalapb/ScalaPB/blob/master/CONTRIBUTING.md and this is an example commit that adds an option: 82bbd69 |
Thanks for the pointers -- I'll give it a shot. |
@dsilvasc : 1. is it something that you still need? 2. Will you be able to give it a shot? |
Closing due to inactivity. Please feel free to comment if there's still interest in it and we can re-open. |
Was there ever any attempt for this? |
In cases where I control the proto and am willing to live with backwards compatibility risks, it'd be great to be able to apply |
Sealed oneofs are only generated when the oneof name is
sealed_value
. For people with existing schemas (or schemas shared across multi-language teams where others might prefer another name), would it be possible to allow annotating the message or the oneof?Maybe something like
option (scalapb.message).sealed_oneof = true
?The text was updated successfully, but these errors were encountered: