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
I'm interested in receiving JSON-encoded Foo messages where the enum might have more values added to it later, without me having to update my Proto file and re-generate code. Both of these JSON blobs deserialize fine: {"myEnum": "MY_ENUM_UNSPECIFIED"} and {"myEnum": 1}. However, these two won't work: {"myEnum": "MY_ENUM_BUX"} and {"myEnum": 100}.
It would be great if some sort of mechanism could be added to tolerate unknown enum values.
The text was updated successfully, but these errors were encountered:
Consider the following Proto file:
I'm interested in receiving JSON-encoded
Foo
messages where the enum might have more values added to it later, without me having to update my Proto file and re-generate code. Both of these JSON blobs deserialize fine:{"myEnum": "MY_ENUM_UNSPECIFIED"}
and{"myEnum": 1}
. However, these two won't work:{"myEnum": "MY_ENUM_BUX"}
and{"myEnum": 100}
.It would be great if some sort of mechanism could be added to tolerate unknown enum values.
The text was updated successfully, but these errors were encountered: