[material_ui] Add material_ui package#11043
Conversation
![gemini-code-assist[bot]](proxy.php?url=https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces the new material_ui package as part of the effort to decouple the Material library from the Flutter framework. The changes include the necessary boilerplate for a new Dart package, such as the pubspec.yaml, README.md, and a placeholder library file that re-exports package:flutter/material.dart. The overall structure is sound. I have one suggestion to enhance the pubspec.yaml for better package presentation on pub.dev.
packages/material_ui/pubspec.yaml
Outdated
| @@ -0,0 +1,22 @@ | |||
| name: material_ui | |||
| description: The Flutter Material Design Library | |||
There was a problem hiding this comment.
The package description is quite brief. For better discoverability and to provide more context for users on pub.dev, it's recommended to have a description between 60 and 180 characters. A more detailed description would help developers understand the package's purpose at a glance.
description: The official Flutter package for Material Design, providing a rich set of widgets to build UIs that follow the Material Design specification.There was a problem hiding this comment.
I think this may actually fail publishing because of a pub warning, so we should fix this (in both packages).
packages/material_ui/pubspec.yaml
Outdated
| @@ -0,0 +1,22 @@ | |||
| name: material_ui | |||
| description: The Flutter Material Design Library | |||
There was a problem hiding this comment.
I think this may actually fail publishing because of a pub warning, so we should fix this (in both packages).
|
The CI! It passes! 🥳 |
stuartmorgan-g
left a comment
stuartmorgan-g
left a comment
There was a problem hiding this comment.
LGTM!
Once this lands and publishes I'll go update the publisher to flutter.dev (this has to be done manually for each new package); if I forget and you see it showing unverified publisher, just ping me.
flutter/packages@59f905c...9da22bf 2026-02-19 [email protected] [cupertino_ui, material_ui] Fix capitalization in README section headers (flutter/packages#11058) 2026-02-18 [email protected] Manual roll Flutter from 6e4a481 to c023e5b (17 revisions) (flutter/packages#11060) 2026-02-18 [email protected] [vector_graphics_compiler] support percentage units SVG shape attributes (flutter/packages#10577) 2026-02-18 [email protected] [local_auth] Convert example app to Swift (flutter/packages#11003) 2026-02-18 [email protected] [ci] Fix syntax error in auto-labeler (flutter/packages#11052) 2026-02-18 [email protected] Refactor Github Action per b/485167538 (flutter/packages#11051) 2026-02-18 [email protected] [material_ui] Add material_ui package (flutter/packages#11043) 2026-02-18 [email protected] [cupertino_ui] Add cupertino_ui package (flutter/packages#11042) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages-flutter-autoroll Please CC [email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
…r#182611) flutter/packages@59f905c...9da22bf 2026-02-19 [email protected] [cupertino_ui, material_ui] Fix capitalization in README section headers (flutter/packages#11058) 2026-02-18 [email protected] Manual roll Flutter from 6e4a481 to c023e5b (17 revisions) (flutter/packages#11060) 2026-02-18 [email protected] [vector_graphics_compiler] support percentage units SVG shape attributes (flutter/packages#10577) 2026-02-18 [email protected] [local_auth] Convert example app to Swift (flutter/packages#11003) 2026-02-18 [email protected] [ci] Fix syntax error in auto-labeler (flutter/packages#11052) 2026-02-18 [email protected] Refactor Github Action per b/485167538 (flutter/packages#11051) 2026-02-18 [email protected] [material_ui] Add material_ui package (flutter/packages#11043) 2026-02-18 [email protected] [cupertino_ui] Add cupertino_ui package (flutter/packages#11042) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages-flutter-autoroll Please CC [email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
3 participants
Creates the material_ui package in preparation for decoupling.
Once published, this will be marked as
unlisted(to be done in pub.dev dashboard) until the primary code move from the framework takes place.Pre-Review Checklist
[shared_preferences]pubspec.yamlwith an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under1.CHANGELOG.mdto add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under1.///).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.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 ↩3