fix(deps): update dependency flex_color_picker to v3.6.0 #1381
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.
This PR contains the following updates:
3.5.1
->3.6.0
Release Notes
rydmike/flex_color_picker (flex_color_picker)
v3.6.0
Compare Source
September 25, 2024
NEW
The ColorPicker got the following new properties and features:
Boolean
showEditIconButton
, defaults tofalse
.colorCodeReadOnly
is false. Tapping the icon button will focus the color code entry field.IconData
editIcon
, defaults toIcons.edit
.Boolean
focusedEditHasNoColor
, defaults tofalse
.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.Boolean
tonalPaletteFixedMinChroma
, defaults tofalse
.FIX
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 fromfalse
totrue
, to match the actual default behavior it has had since version 3.4.0, and the behavior that should be preferred. Thefalse
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 usefalse
at all, but for now it is fixed again.TESTS
Configuration
📅 Schedule: Branch creation - "after 6pm every weekday,every weekend" in timezone Australia/Sydney, Automerge - "after 6pm every weekday,every weekend" in timezone Australia/Sydney.
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.