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
This is because _$shapePropertyEnumMap[k] yields type String?, even though the value - I think - is guaranteed to exist in the map. This isn't a major problem unless you have post processing (I'm using FakeFirebaseFirestore, but there could be otherwise).
This causes a problem with anything which is doing null-aware runtime typechecking for Map<String, dynamic>.
json_serializable: "6.2.0"
The text was updated successfully, but these errors were encountered:
#1146)
Before this change, serializing non-nullable enums in a subtype was incorrectly producing nullable string types.
For example, serializing a class member of type Map<enum, String> produced a type Map<String?, dynamic> where Map<String, dynamic> should have been produced.
Nullable enums should still produce nullable types, eg. serializing List<enum?> should produce List<String?>
fixes#1145
Using an Enum as a key in a map yields a field with type <String?, dynamic> (rather than the expected <String, dynamic>.
This leads to the generated code;
This is because _$shapePropertyEnumMap[k] yields type String?, even though the value - I think - is guaranteed to exist in the map. This isn't a major problem unless you have post processing (I'm using FakeFirebaseFirestore, but there could be otherwise).
This causes a problem with anything which is doing null-aware runtime typechecking for Map<String, dynamic>.
json_serializable: "6.2.0"
The text was updated successfully, but these errors were encountered: