-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Remove double MaterialApp wrap from api samples #150055
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@bleroux @TahaTesser Can I ask you to watch out for this pattern in reviews of API sample tests? If the widget under test already includes a MaterialApp we don't want the test to double-wrap it in another MaterialApp in the test. This can inadvertently hide problems in the API sample code (as an example see #150018). |
gspencergoog
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the reminder. We'll watch out for this. |
The widget under test already contains a MaterialApp, so there's no need to wrap it again with one in the test. In fact, the additional MaterialApp could hide problems in the widget under test.
The widget under test already contains a MaterialApp, so there's no need to wrap it again with one in the test. In fact, the additional MaterialApp could hide problems in the widget under test.

The widget under test already contains a MaterialApp, so there's no need to wrap it again with one in the test. In fact, the additional MaterialApp could hide problems in the widget under test.