Repository navigation
deps: Add some overrides to unblock Flutter Color API changes for wide-gamut - #920
Conversation
…e-gamut This commit follows the request in flutter/flutter#154123 by pointing to a Flutter maintainer's fork of `flutter_color_model` and `color_model` while we wait for their PR from that fork to be settled. To validate this change, I checked out the roll from engine-flutter-autoroll that failed on our tests: flutter/flutter#153985 and confirmed that our tests (the ones that run with `tools/check test --all`) failed with same-looking errors before this change and passed after this change. I did run all of `tools/check --all`, not just the `test` suite. There was "info"-level output from the analyzer telling us about things we've been using that will be deprecated with the proposed Color API change (`Color.value` and `Color.withOpacity`). We'll want to respond promptly to these deprecation notices -- and in fact our CI treats this "info"-level output as an error -- but I think we can leave that out of scope for the customer-tests fix, because we've set it so "info"-level analyzer output isn't fatal there: flutter/tests@54cc35f9f#diff-d2bef7bb93d58c3db877456685dad3e25d1546c1fc318e9d6c560e91c457eaa7R10
|
I think it is concerning that we rely on packages whose maintainer does not seem to be active anymore. Maybe that's a sign that we should eventually drop the dependency after this fix, but I'm not sure how much work that will be. |
|
Tested and could verify that the fix works. LGTM! |
|
Thanks for the review! Merging.
Interesting, yeah. I guess a helpful signal for the maintainer's engagement will be to see how quickly they respond to james-alex/color_models#10 . 🙂 |
|
Thanks everyone for moving on this quickly. This is kind of a weird flow, forward fixing things. It tested fine locally so hopefully I got everything right 🤞 |
And update Flutter's supporting libraries to match. Also, as anticipated in zulip#920 (see PR description), handle some deprecations in the Color API from flutter-team-archive/engine@eff1b76cf (rolled in flutter/flutter@8c1a93508). Deprecation warnings are "info"-level in analyzer output, and CI treats that as fatal, because we don't want to let those hang around. In particular, `withOpacity` is replaced with the new `withValues`. Also, `value` is newly deprecated, but we migrated off that in the previous commit.
3 participants
This commit follows the request in
flutter/flutter#154123
by pointing to a Flutter maintainer's fork of
flutter_color_modelandcolor_modelwhile we wait for their PR from that fork to be settled.To validate this change, I checked out the roll from engine-flutter-autoroll that failed on our tests:
flutter/flutter#153985
and confirmed that our tests (the ones that run with
tools/check test --all) failed with same-looking errors before this change and passed after this change.I did run all of
tools/check --all, not just thetestsuite. There was "info"-level output from the analyzer telling us about things we've been using that will be deprecated with the proposed Color API change (Color.valueandColor.withOpacity). We'll want to respond promptly to these deprecation notices -- and in fact our CI treats this "info"-level output as an error -- but I think we can leave that out of scope for the customer-tests fix, because we've set it so "info"-level analyzer output isn't fatal there:flutter/tests@54cc35f9f#diff-d2bef7bb93d58c3db877456685dad3e25d1546c1fc318e9d6c560e91c457eaa7R10