Committed by
GitHub
Remove redundant breaking change notice for Map<Object?, Object?> change
The analyzer accepts `Map` and `Map<Object?, Object?>` without restrictions. Thus this is actually not a breaking change.
Showing
1 changed file
with
0 additions
and
3 deletions
| 1 | ## NEXT | 1 | ## NEXT |
| 2 | -Breaking changes: | ||
| 3 | -* The internal `fromNative()` methods now accept a `Map<Object?, Object?>` instead of `Map<dynamic, dynamic>`. | ||
| 4 | - | ||
| 5 | Improvements: | 2 | Improvements: |
| 6 | * The `type` of an `Address` is now non-null. | 3 | * The `type` of an `Address` is now non-null. |
| 7 | * The `type` of an `Email` is now non-null. | 4 | * The `type` of an `Email` is now non-null. |
-
Please register or login to post a comment