FlexColorScheme Files

8.2.0

March 23, 2025

Package

CHORE * Update the package to support and require at least Flutter v3.29.0. * Remove all usage and references to new deprecated properties in Flutter 3.29.0: * MaterialStateUnderlineInputBorder → WidgetStateInputBorder * MaterialStateOutlineInputBorder → WidgetStateInputBorder * Themedata.dialogBackgroundColor: Removed all usage and references in the FCS packages and Themes Playground app. * Remove all usage and references to new deprecated properties in Flutter 3.31.0 BETA: * ThemeData.indicatorColor: Removed all usage and references in the FCS packages and Themes Playground app. FlexColorScheme has not used this property for a while, but kept it defined while it still existed. It is deprecated in Flutter 3.31.0 BETA and will be so in next stable Flutter release as well. FCS 8.2.0 stops defining any value for it and also removes it from the Themes Playground app. It has in FCS for a long time already been replaced by TabBarThemeData.indicatorColor. Test were now also updated to use this reference instead of the to be deprecated one. * Fix lints for the stable, beta and master channels.
* FlexColorScheme is still using pre-Dart 3.7.0 formatter. It will change to new format, with longer line length, when the Flutter stable channel supports manual trailing comma. Change to the new formatter was tested, but reverted because it was horrible.

FIX * Fix TabBarTheme normalization Flutter SDK breaking change on the master and beta channel, see issue [#276]. * The TabBar theme API had breaking changes in Flutter 3.27 release. These were addressed in FlexColorScheme v8.1.0. In Flutter 3.31 (beta) there are additional compile-time breaking changes not present in Flutter 3.29 and earlier versions. FlexColorScheme v8.2.0 is compatible with these Flutter SDK breaking changes. For more information, see the TabBar theme API breaking changes, that documented the in Flutter 3.27 breaking changes. Apparently, something more changed now, as the TabBar theming that still works in Flutter 3.29, broke again in Flutter 3.31 beta and later. Regardless of what and why it was broken, FCS v8.2.0 fixes the usage of the compile-time broken API, it now works again, with at release time used APIs in Flutter stable, beta and master channels.

NEW * Beta feature: * Added Shadcn UI color schemes. This includes, custom classes to store the Shadcn color tokens, FlexSchemeColor implementations of them and FlexScheme enums of the configs to make it easy to use them.

The `FlexScheme` enums for using the Shadcn colors are:
* `FlexScheme.shadBlue`
* `FlexScheme.shadGray`
* `FlexScheme.shadGreen`
* `FlexScheme.shadNeutral`
* `FlexScheme.shadOrange`
* `FlexScheme.shadRed`  
* `FlexScheme.shadRose`
* `FlexScheme.shadSlate`
* `FlexScheme.shadStone`
* `FlexScheme.shadViolet`
* `FlexScheme.shadYellow`
* `FlexScheme.shadZinc`

• The Shadcn color schemes are still considered beta. The current version does not yet support or use the Shadcn default colors for background, surface and container colors. In this release those colors are using FlexColorScheme's monochrome surface colors. Later versions may change this and use the Shadcn surface colors by default when selecting these themes, with an option to switch to FlexColorScheme's monochrome surface colors, which this version currently uses as the only choice.
• The Shadcn color selections only set default colors, you will have to theme Material to look more like Shadcn yourself by selecting the correct Material components and modifying their properties to look and behave more like Shadcn style. The Themes Playground includes a pre-configured very preliminary configuration that you can use to do this.
• The Shadcn color features are in this beta release excluded from FlexColorScheme's otherwise rigorous tests.

Themes Playground

FIX * Playground: Fix code gen for the first scheme, see issue [#275].

CHANGE * Fix/improve code gen for the second and third Playground scheme. It now exports these schemes the way they are defined internally in the Playground app, instead of as their configuration resulting colors. * Improved the theme code gen order and added some comments to the generated code to make it easier to understand what the main parts do. * Removed the theme codegen option used to generate a config to be pasted directly into MaterialApp properties theme and themeDark, in favor of the newer one that generates the configs as its own file. The newer one has been the default option since version 8.0.0. * Updated TabBar "Known issues" info-expand to state that the broken elastic indicator animation is fixed in Flutter 3.27.3. * The NavigationRail default configuration in the Playground is now NavigationRailLabelType.none. * This is already the default in the FlexColorScheme package and in Flutter SDK. This default value is used to avoid the issue that Flutter SDK only supports using the none option as the collapsed style, when the rail is expanded. For more info about this peculiar limitation see issue [#277]. * Added an info-expand to the NavigationRail panel to explain this known-issue. * You can work around this issue, but only on component config level, by setting the labelType to NavigationRailLabelType.none when extended is set to true, and back to null when it is false to use a themed value, that may then have another value than none when the rail is collapsed. This is a limitation in Flutter SDK, not in FlexColorScheme. The Playground app uses this workaround to avoid the issue when it displays the demo NavigationRail in the extended state.

NEW * Added showing all existing Material-Cupertino platform adaptive widgets. Switch already existed but now also added: * AlertDialog.adaptive * Slider.adaptive * Checkbox.adaptive
* Radio.adaptive * BETA * Added a built-in config for a Shadcn UI like config to the Premade Designs panel. This is only a first rough beta config. * This style configures the Material theme to look a bit like the Shadcn UI design system. It is not an exact replica and never will be, consider it more like inspired by Shadcn. It is primarily intended to be used with the Shadcn theme colors, but you can of course use it with any of the built-in schemes. This is a preliminary first config and will be refined over time as more theming features are added to the Playground that allow us to bring it closer to the Shadcn design. Be aware that the results you get when you use this configuration WILL change in future Themes Playground releases. As always, export your settings and save them as JSON if you want to keep them and use them later again in the Playground.