fix: update color property accessors to match Flutter's stable API #281
+3
−3
Conversation
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
marandaneto
reviewed
Feb 11, 2026
marandaneto
reviewed
Feb 12, 2026
| final b = color.blue; | ||
| final r = (color.r * 255.0).round().clamp(0, 255); | ||
| final g = (color.g * 255.0).round().clamp(0, 255); | ||
| final b = (color.b * 255.0).round().clamp(0, 255); |
Member
There was a problem hiding this comment.
@ioannisj can you double check if the changes make sense now?
since we do some stuff after re hsp, if all good, we can merge it
marandaneto
approved these changes
Feb 12, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
💡 Motivation and Context
To avoid a info lint about deprecation.
Related PR on Flutter.
This would improve the pub points on pub.dev
💚 How did you test it?
When applied the change, the lint was solved
📝 Checklist