Support stripping enums prefixes#119
Merged
smnbbrv merged 1 commit intosmnbbrv:masterfrom Nov 14, 2025
Merged
Conversation
Owner
|
Hi @EraYaN please check the failed pipeline. This is also a breaking change, please use proper semantic-release commit message |
EraYaN
force-pushed
the
enum-stripping
branch
from
2b01529 to
f13fa27
Compare
Contributor
Author
|
I think I have fixed the linter errors and I have made the behavior an option which is really the better approach anyway. |
EraYaN
force-pushed
the
enum-stripping
branch
from
f13fa27 to
98ed7ab
Compare
Owner
|
Thanks! is released under 5.0.0 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This matches the behavior of say the C# generators in
protoc. And given that in the newer editions they seem to be enforcing this prefixing in enums, it would be a great feature to reduce the amount of stuff you have to type when using the generated types. We have been using this on the 3.1.2 version for a couple of years now.Fixes #112