Repository navigation
Migrate examples/splash to package:material_ui - #190248
Conversation
There was a problem hiding this comment.
Code Review
This pull request replaces the official package:flutter/material.dart import with a third-party package:material_ui/material_ui.dart dependency in the splash example and its tests. Feedback from the reviewer highlights that Flutter examples must rely solely on the official Flutter SDK to prevent supply chain security risks, and recommends reverting these changes to use the official package.
d5dc5ed to
008eb3b
Compare
justinmc
left a comment
There was a problem hiding this comment.
LGTM but we should hold off until this comment is addressed #190237 (comment).
|
Now that #190237 is merged I think you just need to update this branch and it should pass CI. |
008eb3b to
a774577
Compare
|
autosubmit label was removed for flutter/flutter/190248, because - The status or check suite Tree_analyze has failed. Please fix the issues identified (or deflake) before re-applying this label. |
|
There's a failure saying that you need to run |
a774577 to
dbca5e3
Compare
|
autosubmit label was removed for flutter/flutter/190248, because - The status or check suite Google testing has failed. Please fix the issues identified (or deflake) before re-applying this label. |
fbdc436 to
ebf22e0
Compare
Work towards #190093
Migrates
examples/splashtomaterial_uiPre-Review Checklist
[shared_preferences]///).If you need help, consider asking for advice on the #hackers-new channel on Discord.
Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the
gemini-code-assistbot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.Test exemption: Migration only.
Footnotes
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩2