-
Notifications
You must be signed in to change notification settings - Fork 28.7k
Remove nullOk
parameter from Cupertino color resolution APIs
#68905
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
Conversation
c29fe74
to
0098e22
Compare
0098e22
to
bb571de
Compare
This currently contains the changes also in #68905 Once that lands, I'll rebase this and take it off of draft status. |
53142c5
to
fbebac6
Compare
Rebased and ready for review now. This does slightly change the mechanics of these functions: specifying Let me know if that seems like a bad idea... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thank you!
fbebac6
to
2fde09f
Compare
2fde09f
to
641f566
Compare
Description
This removes the
nullOk
parameter from the Cupertino color resolution APIs. It changes the behavior ofCupertinoDynamicColor.resolveFrom
to not throw if the context does not contain the required dependencies, which was the default (and was only set to throw in a test). This allows a cascade of being able to remove thenullOk
parameter from several other APIs, where they didn't actually return nullable values anyhow, it just indicated that the throwing behavior would be enabled if set to false, which made it a pretty confusing name.Related Issues
Tests
Breaking Change