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
{{ message }}
Repository navigation
Some classes override operator == with a nullable parameter #117838
At runtime, a null value is never passed to ==. No class should ever expect that it might get a nullable type.
I see the following two operator == overrides which accept a nullable parameter:
warning • The parameter type of '==' operators should be non-nullable • packages/flutter/lib/src/material/about.dart:759:17 • non_nullable_equals_parameter
warning • The parameter type of '==' operators should be non-nullable • packages/flutter/test/rendering/mouse_tracker_cursor_test.dart:465:17 • non_nullable_equals_parameter
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
github-actions commentedon Mar 4, 2023
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.[flutter_image] [flutter_markdown] Do not use dynamic in an == operat…
[flutter_image] [flutter_markdown] Do not use dynamic in an == operat…
[flutter_image] [flutter_markdown] Do not use dynamic in an == operat…