feat: oneof=unions-value to use the same field name for oneof cases #1062
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1060.
This adds a new
oneof=unions-value
option that changes how union oneof code is generated. Instead of each case having a field named the same as the$case
, each of them has the same field, calledvalue
. This should simplify writing generic code that can handle multiple cases at once.I chose to make it another option for
oneof=
instead of a separate option since it's just another way of handling oneofs. I also updated the README but it may be a bit much, I'm happy to remove some stuff. I also presumptively suggest that this be the new recommended oneof option.