💄 migrate DebugFloatingThemeButton
to Material 3
#55
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.
Description of the Change
DebugFloatingThemeButton
button was still in Material 2 design because internally it used ToggleButtons.SegmentedButton is a Material 3 version of ToggleButtons, so it was used instead.
debugShowFloatingThemeButton
totrue
in the example app.Padding
to the content of theHomePage
in the example app to make the text better looking.Benefits
More consistency in the package as the migration to Material 3 of the example app was done in version 3.4.1
Possible Drawbacks
I don't see any.
Verification Process
DebugFloatingThemeButton
in the example app.Applicable Issues
None.