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
Currently when an unsupported enum value is found the decoder throws an ArgumentError. This can completely break an app in production when an enum value is added to the server.
Currently the only option is to add an xUnknown value to each enum, which seems completely unnecessary for a nullable value.
It would be great to either add a new property to JsonKey, e.g. allowUnsupportedEnumValue, or handle the same logic if both nullable == true and unknownEnumValue == null.
Currently when an unsupported enum value is found the decoder throws an
ArgumentError
. This can completely break an app in production when an enum value is added to the server.Currently the only option is to add an
xUnknown
value to each enum, which seems completely unnecessary for a nullable value.It would be great to either add a new property to
JsonKey
, e.g.allowUnsupportedEnumValue
, or handle the same logic if bothnullable == true
andunknownEnumValue == null
.The text was updated successfully, but these errors were encountered: