build(deps): bump flex_color_scheme from 7.3.1 to 8.0.2

[dependabot]

Bumps flex_color_scheme from 7.3.1 to 8.0.2.

Release notes

Sourced from flex_color_scheme's releases.

Version 8.0.2

8.0.2

Dec 1, 2024

Package

FIX

• Changelog for version 8.0.0 says and intended this:

  "The FlexSubThemesData property inputDecoratorIsFilled now default to false when undefined, like Flutter SDK does. Set it to true to get the same style it had with previous undefined value."

  Due to a bug, this was not the case. This release fixes the bug and the property now defaults to false when undefined, as intended and documented in version 8.0.0 changelog. FIX: rydmike/flex_color_scheme#265

Version 8.0.1

8.0.1

Nov 13, 2024

Package

FIX

• Fixed the version constraint. The V8 package is only compatible with Flutter 3.24.0 and later. It was intended to be compatible with Flutter 3.22.0 and later, but a theming API that is only available in Flutter version 3.24.0 and later made it into the release. If you need a release of version 8 that is also compatible with Flutter 3.22.x, you can use version 8.0.1-dev.3.22 of the package. That package release is identical to this release, but excludes the API not available in Flutter 3.22.0.

Themes Playground

NEW

• Added a quick share button on the side menu. It exports the Playground settings to JSON, makes a URL of it and copies the result to the clip board in one go. Ready to be shared where needed.

CHANGE

• Made changes to the Playground to make it possible to compile it to a Web WASM-GC build. The Playground WASM build is still experimental and not yet published anywhere.

Version 8.0.1-dev.3.22

8.0.1-dev.3.22

Nov 13, 2024

Package

FIX

• This is a special release of FlexColorScheme version 8, it is identical to release 8.0.1, but it removes the locale API from the InputDecorationTheme to keep version 8 compatible with Flutter 3.22.x. If you use Flutter 3.24 or later, you should use the 8.0.0 or later releases instead.

... (truncated)

Changelog

Sourced from flex_color_scheme's changelog.

8.0.2

Dec 1, 2024

Package

FIX

• Changelog for version 8.0.0 says and intended this:

  "The FlexSubThemesData property inputDecoratorIsFilled now default to false when undefined, like Flutter SDK does. Set it to true to get the same style it had with previous undefined value."

  Due to a bug, this was not the case. This release fixes the bug and the property now defaults to false when undefined, as intended and documented in version 8.0.0 changelog. FIX: rydmike/flex_color_scheme#265

8.0.1

Nov 13, 2024

Package

FIX

• Fixed the version constraint. The V8 package is only compatible with Flutter 3.24.0 and later. It was intended to be compatible with Flutter 3.22.0 and later, but a theming API that is only available in Flutter version 3.24.0 and later made it into the release. If you need a release of version 8 that is also compatible with Flutter 3.22.x, you can use version 8.0.1-dev.3.22 of the package. That package release is identical to this release, but excludes the API not available in Flutter 3.22.0.

Themes Playground

NEW

• Added a quick share button on the side menu. It exports the Playground settings to JSON, makes a URL of it and copies the result to the clip board in one go. Ready to be shared where needed.

CHANGE

• Made changes to the Playground to make it possible to compile it to a Web WASM-GC build. The Playground WASM build is still experimental and not yet published anywhere.

8.0.0

Nov 3, 2024

SUMMARY

Version 8.0.0 makes FlexColorScheme fully aligned with Flutter's MAJOR BREAKING Material-3 theming changes introduced in Flutter version 3.22. Due to Flutter 3.22 breaking many past Material styles, introducing new colors to ColorScheme and deprecating three colors, FlexColorScheme had to undergo major revision and also break many of its past styles and some older APIs.

Most APIs are still there and work as before, but a few produce results that differ slightly from past ones, just like Flutter 3.22 also does over previous versions. Generally, the upgrade should be smooth, but you may need to review the produced theme result to see that you don't get any changes that don't fit with your design goals. Some past defaults have changed in FCS V8, but previous settings are still available. However, you will need to enable them explicitly to get the same results as before. The purpose of these default value changes is to make FCS have less opinionated defaults, and be more aligned with Flutter's Material-3 design defaults. The Themes Playground app will still have some of its own opinionated defaults, done via default settings values the app uses in its default configuration, but the package Material-3 default starting points are now much more aligned with Flutter's Material-3 defaults.

In the Themes Playground you can now export and import settings to a JSON file, and import them back into the Playground later. This is a great way to save your theme settings for later re-use. The exported JSON contains all the internal controller settings values you have configured in the Playground app, that are needed to restore a given configuration state. This Playground feature was a nice contribution by GitHub user @​akiller in !PR 257, thank you! This contributed feature got enhanced with more error handling and a slightly refined UI to make it production ready. As a further enhancement of the JSON export feature, the Themes Playground app also got the ability to convert the exported settings JSON config to a shareable URL. You can now share Playground settings with other Flutter developers.

... (truncated)

Commits

• a57c6a1 Action: Deploy GH pages on publish
• 9a31397 FIX: rydmike/flex_color_scheme#265
• fa03008 FIX: Playground share URL https://github.com/rydmike/flex_color_scheme/issues...
• bd9a651 ADD: Wasm run config for VS-Code
• 1c4f66e Actions: Set needed triggers for GitHub Pages Web build
• d8897f9 WEB: Wasm Build 06 Use No-strip-wasm and turn of Hive logging
• e0dbec8 Update pubspec.yaml
• d1df55b Bump: Web build
• ca30773 FIX: Playground WASM SVG load
• 8f871da Update deploy_playground_netlify.yml
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #71.