Conversation
…e it in own file so we need to export it too.
…e min 3.8.0 when jumping to longer lines, like 120
…tter explanations
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #23 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 41 43 +2
Lines 2960 2916 -44
=========================================
- Hits 2960 2916 -44 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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
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.
4.0.0
Nov 22, 2025
The version requires Flutter 3.38.0 or higher.
This release really brings the bundled forked version of the package Material Color Utilities (MCU) to parity with version 0.13.0. Flutter stable 3.38.x still uses MCU 0.11.1. Next version of Flutter, after stable 0.38, will use MCU 0.13.0, see PR 12125.
This FSS release contains a breaking change to match the default for expressive on-container colors in MCU 0.12.0. This is also included in the coming bump to MCU 0.13.0 in Flutter after version 3.38.
BREAKING
SeedColorScheme.fromSeedsparameteruseExpressiveOnContainerColorsnow defaults totrueinstead offalse.SeedColorScheme.fromSeedsmatch the default behavior of MCU 0.12.0 and later, where expressive on-container colors are used by default in light mode.useExpressiveOnContainerColorstofalsewhen callingSeedColorScheme.fromSeeds.DynamicSchemeparametercustomErrorPalettewas renamed toerrorPaletteto match newly exposed MCU 0.13.0 naming.customErrorPaletteinDynamicScheme. It is very unlikely to be used directly by end users of this package, as it is a very low-level API and not used by recommended main public APIs directly, but it was a public API, unfortunately.intproperties inFlexSeedScheme._()and same named publicColorparameters inSeedColorScheme.fromSeeds():backgroundonBackgroundsurfaceVariantintproperties inFlexTones(),FlexTones.light()andFlexTones.dark()and same named parameters inFlexTones.copyWith():backgroundToneonBackgroundTonesurfaceVariantToneCHANGE
FlexSchemeVariantand theirconfigDetailsdescriptions to offer better explanations.FlexSchemeVariant, any changes in the property valuesvariantName,description,configDetails,iconandshadeare not considered breaking changes, only patches.FlexColorSchemepackage example apps, like the Themes Playground.CHORE
MathUtils.sanitizeDegreesDoublefor hue calculation in Cam16. (MCU update Nov 19, 2025, not yet in any package version)KeyColoralgorithm and its binary search optimization that was added in MCU 0.11.2. This may improve performance when extracting tonal palettes from seed colors.TESTS
useExpressiveOnContainerColorsdefaulting totrue.DynamicSchemeVariants to ensure they can be created without errors, so that sameDynamicSchemematches results from Flutter'sColorScheme.fromSeedusing correspondingDynamicSchemeVariant. The loop test excludes the variantsDynamicSchemeVariant.fidelity,DynamicSchemeVariant.monochromeandDynamicSchemeVariant.contentthat have their own special tone logic. Previously only the defaultDynamicSchemeVariant.tonalSpotwas tested this way. This test helps us verify that our fork of MCU can match the version of MCU that Flutter uses internally. When Flutter stable changes to use MCU 0.13.0, this test will need to change its flaguseExpressiveOnContainerColorsfromfalsetotrue.Note
Release 4.0.0 (min Flutter 3.38): sync bundled MCU to ~0.13, default expressive on-container colors, rename error palette param, remove deprecated fields/tones, update docs/examples/tests/CI.
useExpressiveOnContainerColorsdefaults totrueinSeedColorScheme.fromSeedsand Flex APIs; example app toggles updated.DynamicSchemeparam renamedcustomErrorPalette→errorPalette.background,onBackground,surfaceVariant(and related tones) from public APIs.KeyColor(binary search), switch hue sanitization, const-ify internals, API tweaks (constructors takesourceColorHct).CorePalettes; equality/hash improvements.4.0.0; README/CHANGELOG updated; demo links/assets moved todemo-v4.>=3.38.0and Dart>=3.6.0; deps updated (collection1.19.x,meta1.17.0,flex_color_picker3.7.2).v4.DynamicSchemeVariants); adjust expectations for new defaults.Written by Cursor Bugbot for commit 047daf8. This will update automatically on new commits. Configure here.