-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Simplify if-else block into single return statement
#175574
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
Simplify if-else block into single return statement
#175574
Conversation
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.
Code Review
This pull request correctly simplifies several if-else blocks into single return statements, which improves code conciseness. I've added suggestions to further simplify these by converting the single-line function bodies into arrow functions, which is a common practice for cleaner code and aligns with the Effective Dart style guide.
| trackVisibility: WidgetStateProperty.resolveWith((Set<WidgetState> states) { | ||
| if (states.contains(WidgetState.hovered)) { | ||
| return true; | ||
| } | ||
| return false; | ||
| return states.contains(WidgetState.hovered); | ||
| }), |
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.
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.
@justinmc Do you prefer the arrow function too?
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.
I don't think there's any con to using the arrows, but I might be wrong.
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.
Great, I updated the code to use expression body in Use expression body
| trackVisibility: WidgetStateProperty.resolveWith((Set<WidgetState> states) { | ||
| if (states.contains(WidgetState.hovered)) { | ||
| return true; | ||
| } | ||
| return false; | ||
| return states.contains(WidgetState.hovered); | ||
| }), |
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.
| trackVisibility: WidgetStateProperty.resolveWith((Set<WidgetState> states) { | ||
| if (states.contains(WidgetState.hovered)) { | ||
| return true; | ||
| } | ||
| return false; | ||
| return states.contains(WidgetState.hovered); | ||
| }), |
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.
| trackVisibility: WidgetStateProperty.resolveWith((Set<WidgetState> states) { | ||
| if (states.contains(WidgetState.hovered)) { | ||
| return true; | ||
| } | ||
| return false; | ||
| return states.contains(WidgetState.hovered); | ||
| }), |
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.
| trackVisibility: WidgetStateProperty.resolveWith((Set<WidgetState> states) { | ||
| if (states.contains(WidgetState.hovered)) { | ||
| return true; | ||
| } | ||
| return false; | ||
| return states.contains(WidgetState.hovered); | ||
| }), |
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.
| trackVisibility: WidgetStateProperty.resolveWith((Set<WidgetState> states) { | ||
| if (states.contains(WidgetState.hovered)) { | ||
| return true; | ||
| } | ||
| return false; | ||
| return states.contains(WidgetState.hovered); | ||
| }), |
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.
| WidgetStateProperty.resolveWith((Set<WidgetState> states) { | ||
| if (states.contains(WidgetState.hovered)) { | ||
| return true; | ||
| } | ||
| return false; | ||
| return states.contains(WidgetState.hovered); | ||
| }), |
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.
victorsanni
left a comment
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.
This PR qualifies for a test exemption.
| trackVisibility: WidgetStateProperty.resolveWith((Set<WidgetState> states) { | ||
| if (states.contains(WidgetState.hovered)) { | ||
| return true; | ||
| } | ||
| return false; | ||
| return states.contains(WidgetState.hovered); | ||
| }), |
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.
I don't think there's any con to using the arrows, but I might be wrong.
6c2d429 to
20cf1b7
Compare
dkwingsmt
left a comment
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 for the cleanup!
|
autosubmit label was removed for flutter/flutter/175574, because The base commit of the PR is older than 7 days and can not be merged. Please merge the latest changes from the main into this branch and resubmit the PR. |
20cf1b7 to
5fc8562
Compare
…-return-statement
Follow up of flutter#175396 This PR applies the code change suggestion from gemini review ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [ ] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md --------- Co-authored-by: Tong Mu <[email protected]>
Follow up of #175396
This PR applies the code change suggestion from gemini review
Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.
Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the
gemini-code-assistbot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.