You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These options should be made available in the generated code as JSON, just like field and service / method options already are.
Implementation is probably not straight-forward because there is no good place to put the data. One approach could be to use symbols to add the options to a hidden property on the TypeScript enum object.
The text was updated successfully, but these errors were encountered:
In another plugin I was using, I managed to do this in a way by processing the Leading comments for each value.
But recently I found out the "EnumValueOptions" and wondered if this is fit for it.
Is it possible to use this in the way it was intended for the EnumValueOptions, or should I continue with my custom implementation?
FYI: I'm currently using the ".proto" files to simply generate the code in Typescript, C# and Python. This means that the Textual value is only used for visualisation purposes, and we keep the numeric Enumerations for the data transfer.
Protobuf has enum options. For example:
These options should be made available in the generated code as JSON, just like field and service / method options already are.
Implementation is probably not straight-forward because there is no good place to put the data. One approach could be to use symbols to add the options to a hidden property on the TypeScript enum object.
The text was updated successfully, but these errors were encountered: