Repository navigation
Introduce useMaterial3 flag for ThemeData to allow for opt-in - #93434
Merged
Merged
Conversation
flutter-dashboard
Bot
added
p: material_ui
|
Wouldn't an enum be better suited once Material 4 might become a thing in the future? Otherwise we would have two flags |
rami-a
approved these changes
Nov 11, 2021
Contributor
Author
An enum would be better if we planned on keeping this around. However, the currently proposed plan is that |
63 of 70 tasks
guidezpl
changed the title
guidezpl
changed the title
useMaterial3 flag for ThemeData to allow for opt-in
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As part of the migration to Material 3, this PR adds a new
useMaterial3flag toThemeDatathat will allow applications to opt-in to Material 3 changes that are coming to many of the components across the library.Currently there are no components that this affects, but as we migrate each component to M3, they will use this flag to determine which defaults they should use, and this flags doc will be updated.
Pre-launch Checklist
///).