-
Notifications
You must be signed in to change notification settings - Fork 28.5k
Fix outdated reference to material in WidgetStateMapper's error message #166816
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
It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging. If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.If you believe this PR qualifies for a test exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group. |
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.
The material->widget change looks good, but I'm curious about the other change.
'None of the provided map keys matched this set, ' | ||
'and the type "$T" is non-nullable.\n' | ||
'Consider using "WidgetStateProperty<$T?>.fromMap()", ' | ||
'Consider using "WidgetStateMapper<$T?>()", ' |
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.
Can you explain this change here?
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.
It just felt weird that WidgetStateMapper was recommending WidgetStateProperty.fromMap even though it’s inside WidgetStateMapper, they both did the same thing, and fromMap is more verbose.
No strong opinion on it though, I can revert this.
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.
Got it. I say keep it. Thanks for explaining.
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 👍
'None of the provided map keys matched this set, ' | ||
'and the type "$T" is non-nullable.\n' | ||
'Consider using "WidgetStateProperty<$T?>.fromMap()", ' | ||
'Consider using "WidgetStateMapper<$T?>()", ' |
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.
Got it. I say keep it. Thanks for explaining.
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!
Pre-launch Checklist
///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.