Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
deps: Add some overrides to unblock Flutter Color API changes for wid…
…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
- Loading branch information