Doc and Error Message Improvements#60726
Conversation
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat. Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
goderbauer
left a comment
There was a problem hiding this comment.
This is great. Thanks for the clean-up!
| if (!_colorIsUniform) ErrorDescription('BorderSide.color'), | ||
| if (!_widthIsUniform) ErrorDescription('BorderSide.width'), | ||
| if (!_styleIsUniform) ErrorDescription('BorderSide.style'), | ||
| ErrorDescription('is not uniform.'), |
There was a problem hiding this comment.
This error will be grammatically incorrect (is vs. are) if more than one property is not uniform (assuming that can happen).
There was a problem hiding this comment.
Yeah, it is possible for more than one to be listed. I wasn't sure if it was worth handling the is/are. I've tried a tweak, let me know what you think. :)
| if (!_colorIsUniform) ErrorDescription('BorderSide.color'), | ||
| if (!_widthIsUniform) ErrorDescription('BorderSide.width'), | ||
| if (!_styleIsUniform) ErrorDescription('BorderSide.style'), | ||
| ErrorDescription('is not uniform.'), |
|
This pull request is not suitable for automatic merging in its current state.
|
|
This pull request is not suitable for automatic merging in its current state.
|
Description
A couple of weeks ago I did a quarantine doc sprint. 😷 These are the remnants that weren't merged in other PRs.
The goal was to de-clutter the issue tracker of highly upvoted documentation/error message bugs, or those that are also labeled as regressions and crashers.
This may be broken out further into more PRs for clarity. :)
Related Issues
Fixes #19445
Fixes #7659
Fixes #44128
Fixes #13861
Fixes #7703
Fixes #13013
Fixes #14842
Fixes #15423
Fixes #58371
Fixes #47764
Fixes #32701
Fixes #27386
Tests
Just doc changes or assertion refactoring for better messaging.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.