Problem when using optional for enums #300
-
|
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? |
Beta Was this translation helpful? Give feedback.
Answered by
whatyouhide
Nov 26, 2022
Replies: 1 comment
-
|
This needs more investigation, and might be a potential bug. Opening an issue for this. EditMy bad, this was actually already fixed in #302. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
whatyouhide
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This needs more investigation, and might be a potential bug. Opening an issue for this.
Edit
My bad, this was actually already fixed in #302.