Repository navigation
[material_ui] Import of Material tokens v38.0.15 - #12192
Conversation
FolderOrigin-RevId: /google/src/cloud/elliottbrooks/flutter-mwtc-combine-tokens/google3/javascript/materialdesign/tokens/compiler/formats/flutter/staging_output
github-actions
Bot
added
triage-framework
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the material design token data files to version 38.0.15. The changes involve refactoring various UI component tokens, such as App Bar, Chips, Buttons, and Navigation components, to use structured types (TypescaleStruct) instead of individual property definitions. Additionally, several layout and container properties were added or adjusted across these components to align with the updated design system specifications.
elliette
changed the title
|
Just double checking this won't affect the initial release of the material_ui package? As in, none of this is consumed by library code and won't result in visual changes for someone migrating from flutter/material to material_ui? |
That's right! The changes in |
Import of tokens (see cl/944170221)
Pre-Review Checklist
[shared_preferences]///).Test exemption: Import of generated code.
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