[flutter_tool] Use curly braces around single statment control structures#40446
Merged
zanderso merged 1 commit intoflutter:masterfrom Sep 13, 2019
zanderso:curly-braces
Merged
[flutter_tool] Use curly braces around single statment control structures#40446zanderso merged 1 commit intoflutter:masterfrom zanderso:curly-braces
zanderso merged 1 commit intoflutter:masterfrom
zanderso:curly-braces
Conversation
Codecov Report
@@ Coverage Diff @@
## master #40446 +/- ##
==========================================
+ Coverage 58.16% 58.41% +0.25%
==========================================
Files 193 192 -1
Lines 18719 18608 -111
==========================================
- Hits 10888 10870 -18
+ Misses 7831 7738 -93
Continue to review full report at Codecov.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR adds curly braces around single statement control structures that lacked them, and flips the linter flag that enforces this. I'm doing this because:
Related Issues
?
Tests
No change in functionality. Style enforced by analyzer flag going forward.
Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?