Use null-aware elements in NavigationRail#186174
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. |
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
688d89c to
a01e354
Compare
|
CLA is now passing. The remaining failure is the Material/Cupertino code freeze check because this PR touches This is a small cleanup-only change for null-aware collection elements and does not change runtime behavior, so I am happy to wait until the freeze is lifted if needed. |
|
Thanks for your contribution! This PR has reached completion, however we're not able to merge this PR for the moment due to the Material/Cupertino code freeze (#184093). As soon as the decoupling is complete, we will post a way to port this PR to the new packages to land. In the meantime, I'll convert this PR to a draft and apply a label so that we can quickly find it when the freeze is lifted. |
|
I've marked this PR as not ready to port to flutter/packages yet. |
Adopts Dart null-aware elements in
NavigationRailfor the optional trailing widget.This replaces explicit
widget.trailing != nullchecks followed bywidget.trailing!with null-aware collection elements. The behavior stays the same, but the code is cleaner and follows the migration requested in the tracking issue.Part of #172188
Tests
Ran:
All 106 tests passed.
Pre-launch Checklist
///), or this change does not require documentation updates.