Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump flex_color_picker from 3.5.1 to 3.6.0 #82

Merged
merged 1 commit into from
Oct 25, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 26, 2024

Bumps flex_color_picker from 3.5.1 to 3.6.0.

Release notes

Sourced from flex_color_picker's releases.

Version 3.6.0

3.6.0

September 25, 2024

NEW

The ColorPicker got the following new properties and features:

  • Boolean showEditIconButton, defaults to false.

    • Whether to show an edit icon button before the color code field. The edit icon button can be used to give users a visual que that the color code field can be edited. When set to true, the icon button is only shown when the wheel picker is active and colorCodeReadOnly is false. Tapping the icon button will focus the color code entry field.
    • Feature included in updated web demo app: YES
  • IconData editIcon, defaults to Icons.edit.

    • The icon to use on the edit icon button.
    • Feature included in updated web demo app: NO, only default icon used.
  • Boolean focusedEditHasNoColor, defaults to false.

    • Whether the color code entry field should have no color when focused. If the option, to make the color code field have the same color as the selected color is enabled via colorCodeHasColor, it makes it look and double like a big color indicator that shows the selected color. This can also make the edit of the color code confusing, as its color on purpose also changes as you edit and enter a new color value. If you find this behavior confusing and want to make the color code field always have no color during value entry, regardless of the selected color, then set this option to true.
    • Feature included in updated web demo app: YES
  • Boolean tonalPaletteFixedMinChroma, defaults to false.

    • Whether the tonal palette uses a fixed minimum chroma value for all tones, or if it uses the chroma value of the selected color. Prior to version 3.6.0, the tonal palette used minimum chroma value of 48 or chroma of the selected color. This was the default primary tonal palette behavior in Flutter's ColorScheme.fromSeed method before Flutter version 3.22.0. Starting from FlexColorPicker version 3.6.0, the picker creates a HCT color space tonal palette using whatever hue and chroma the selected color has. If you for some reason want to use the old behavior, set this property to true. This will make the tonal palette use the fixed minimum chroma value of 48 for all tones.
    • Feature included in updated web demo app: YES

FIX

  • Since version 3.4.0 the value of property ColorPickerCopyPasteBehavior.editUsesParsedPaste had no impact on the picker's paste behavior when the color code text field was focused. The color picker always behaved as if this property was true. Which incidentally is the behavior that pretty much all uses cases should use. This feature now again works as stated in its doc comments. However, the default value was changed from false to true, to match the actual default behavior it has had since version 3.4.0, and the behavior that should be preferred. The false setting was there to provide color code text field paste behavior backwards compatibility with versions before 2.0.0. We may deprecate this property in a future version, as it is not really recommended to use false at all, but for now it is fixed again.

TESTS

  • Improved the test coverage of the ColorPicker.
Changelog

Sourced from flex_color_picker's changelog.

3.6.0

September 25, 2024

NEW

The ColorPicker got the following new properties and features:

  • Boolean showEditIconButton, defaults to false.

    • Whether to show an edit icon button before the color code field. The edit icon button can be used to give users a visual que that the color code field can be edited. When set to true, the icon button is only shown when the wheel picker is active and colorCodeReadOnly is false. Tapping the icon button will focus the color code entry field.
    • Feature included in updated web demo app: YES
  • IconData editIcon, defaults to Icons.edit.

    • The icon to use on the edit icon button.
    • Feature included in updated web demo app: NO, only default icon used.
  • Boolean focusedEditHasNoColor, defaults to false.

    • Whether the color code entry field should have no color when focused. If the option, to make the color code field have the same color as the selected color is enabled via colorCodeHasColor, it makes it look and double like a big color indicator that shows the selected color. This can also make the edit of the color code confusing, as its color on purpose also changes as you edit and enter a new color value. If you find this behavior confusing and want to make the color code field always have no color during value entry, regardless of the selected color, then set this option to true.
    • Feature included in updated web demo app: YES
  • Boolean tonalPaletteFixedMinChroma, defaults to false.

    • Whether the tonal palette uses a fixed minimum chroma value for all tones, or if it uses the chroma value of the selected color. Prior to version 3.6.0, the tonal palette used minimum chroma value of 48 or chroma of the selected color. This was the default primary tonal palette behavior in Flutter's ColorScheme.fromSeed method before Flutter version 3.22.0. Starting from FlexColorPicker version 3.6.0, the picker creates a HCT color space tonal palette using whatever hue and chroma the selected color has. If you for some reason want to use the old behavior, set this property to true. This will make the tonal palette use the fixed minimum chroma value of 48 for all tones.
    • Feature included in updated web demo app: YES

FIX

  • Since version 3.4.0 the value of property ColorPickerCopyPasteBehavior.editUsesParsedPaste had no impact on the picker's paste behavior when the color code text field was focused. The color picker always behaved as if this property was true. Which incidentally is the behavior that pretty much all uses cases should use. This feature now again works as stated in its doc comments. However, the default value was changed from false to true, to match the actual default behavior it has had since version 3.4.0, and the behavior that should be preferred. The false setting was there to provide color code text field paste behavior backwards compatibility with versions before 2.0.0. We may deprecate this property in a future version, as it is not really recommended to use false at all, but for now it is fixed again.

TESTS

  • Improved the test coverage of the ColorPicker.
Commits
  • 086e776 Set back test action to only run on pull request, not on push
  • 368ee38 Version 3.6.0 Add tests
  • 9e36b40 ADD: Line breaks in About dialog for web demo app
  • f995a21 Version 3.6.0 DRAFT
  • See full diff in compare view

Dependabot compatibility score

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)

Bumps [flex_color_picker](https://github.com/rydmike/flex_color_picker) from 3.5.1 to 3.6.0.
- [Release notes](https://github.com/rydmike/flex_color_picker/releases)
- [Changelog](https://github.com/rydmike/flex_color_picker/blob/master/CHANGELOG.md)
- [Commits](rydmike/flex_color_picker@3.5.1...3.6.0)

---
updated-dependencies:
- dependency-name: flex_color_picker
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dart Pull requests that update Dart code dependencies Pull requests that update a dependency file labels Sep 26, 2024
@coveralls
Copy link

Coverage Status

coverage: 41.892%. remained the same
when pulling a93234c on dependabot/pub/flex_color_picker-3.6.0
into a4dccba on main.

@albertms10 albertms10 merged commit b517542 into main Oct 25, 2024
3 checks passed
@albertms10 albertms10 deleted the dependabot/pub/flex_color_picker-3.6.0 branch October 25, 2024 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dart Pull requests that update Dart code dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants