Convert build mode to lowercase in tool_backend#40393
Conversation
On macOS and iOS, the build mode is converted to lowercase in the Flutter-side script, allowing projects to pass configuration names directly. This adds the same behavior to the tool_backend.dart script currently used by Windows and Linux, so that Windows builds can do the same (since the default configuration names used by VS, as in Xcode, start with a capital letter).
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. While there are exceptions to this rule, if this patch modifies code it is probably not an exception. Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
|
I know longer term Windows and Linux will migrate to |
jonahwilliams
left a comment
There was a problem hiding this comment.
Seems reasonable.
LGTM
Codecov Report
@@ Coverage Diff @@
## master #40393 +/- ##
=========================================
+ Coverage 58.56% 58.67% +0.1%
=========================================
Files 192 192
Lines 18595 18627 +32
=========================================
+ Hits 10890 10929 +39
+ Misses 7705 7698 -7
Continue to review full report at Codecov.
|
On macOS and iOS, the build mode is converted to lowercase in the Flutter-side script, allowing projects to pass configuration names directly. This adds the same behavior to the tool_backend.dart script currently used by Windows and Linux, so that Windows builds can do the same (since the default configuration names used by VS, as in Xcode, start with a capital letter).
Description
On macOS and iOS, the build mode is converted to lowercase in the
Flutter-side script, allowing projects to pass configuration names
directly. This adds the same behavior to the tool_backend.dart script
currently used by Windows and Linux, so that Windows builds can do the
same (since the default configuration names used by VS, as in Xcode,
start with a capital letter).
Related Issues
None
Tests
I added the following tests: None
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
Does your PR require Flutter developers to manually update their apps to accommodate your change?