Prepare for making intl toBeginningOfSentenceCase non-nullable#127488
Prepare for making intl toBeginningOfSentenceCase non-nullable#127488auto-submit[bot] merged 3 commits intoflutter:masterfrom
intl toBeginningOfSentenceCase non-nullable#127488Conversation
I intend to edit `toBeginningOfSentenceCase`'s return value to be non-nullable because it really is never null. That will mean that non-null asserts around it will become flagged as unnecessary, although right now they are necessary. So, apply a workaround - instead use a function that does a non-null assert without triggering any lints even after it becomes unnecessary.
|
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 (don't just cc him here, he won't see it! He's on Discord!). 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. |
|
test-exempt: code refactor with no semantic change FWIW, it's probably fine to just do the entire migration as one PR, if that's easier. |
|
Oh never mind, I misunderstood what API you were planning on changing. |
|
The Linux build_tests_3_3 failure looks like #127611, which was fixed upstream. I'm going to merge in upstream/master to see if that resolves it. |
I intend to edit
toBeginningOfSentenceCase's return value to be non-nullable because it really is never null. That will mean that non-null asserts around it will become flagged as unnecessary, although right now they are necessary. So, apply a workaround - instead use a function that does a non-null assert without triggering any lints even after it becomes unnecessary.