-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Rearrange flutter assemble implementation #36240
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #36240 +/- ##
==========================================
- Coverage 54.8% 54.25% -0.55%
==========================================
Files 187 187
Lines 17246 17208 -38
==========================================
- Hits 9451 9337 -114
- Misses 7795 7871 +76
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #36240 +/- ##
==========================================
- Coverage 55.91% 54.67% -1.25%
==========================================
Files 190 190
Lines 17590 17545 -45
==========================================
- Hits 9836 9592 -244
- Misses 7754 7953 +199
Continue to review full report at Codecov.
|
|
cc @zanderso, did you want to sit down and discuss this PR a bit sometime this week? |
| results.add(file); | ||
| } | ||
| return results; | ||
| } |
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.
In AssetBehavior.outputs the for loop doesn't touch entry.value, so I guess it could instead loop over assetBundle.entries.values instead. I notice that that's what inputs is doing, but inputs is also filtering on the type of the value. If outputs doesn't need to do that as well, then a comment there would be good.
| class AssembleCommand extends FlutterCommand { | ||
| AssembleCommand() { | ||
| addSubcommand(AssembleRun()); | ||
| addSubcommand(AssembleDescribe()); |
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.
Were the describe, etc. subcommands not useful? Have you considered exposing them under flags to assemble for e.g. dependency debugging?
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.
For the iOS case, I need to generate/reference a file for the xcodeproj to read so having this as a command doesn't help. Gradle might be able to use the commands, but probably not as JSON - something like flutter assemble --list-outputs foo which lists the outputfiles on stdout
Description
Updates to flutter assemble
Changes to testing
groups to reduce nesting.