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
Originally posted by nieg675 August 16, 2022
Hello! We are running from commit 48c39d4 to get optional support. However, we experience a problem when using the optional field for enums. If we encode a message that has the optional enum field set to the enum member with tag = 0, we get nil for this field when decoding it. Is this somehow expected, or is it a potential bug?
The text was updated successfully, but these errors were encountered:
whatyouhide
added
Kind:Invalid
An invalid issue: a feature that's already there, a bug not related to this library, and so on.
and removed
Kind:Bug
A bug. Can be a documentation bug, Dialyzer issue, or anything that just "doesn't work".
Kind:Needs More Info
Needs more information to investigate.
labels
Nov 30, 2022
Discussed in #300
Originally posted by nieg675 August 16, 2022
Hello! We are running from commit 48c39d4 to get optional support. However, we experience a problem when using the optional field for enums. If we encode a message that has the optional enum field set to the enum member with tag = 0, we get nil for this field when decoding it. Is this somehow expected, or is it a potential bug?
The text was updated successfully, but these errors were encountered: