Conversation
41b290f to
b8ad042
Compare
5c7a41a to
1749b94
Compare
|
Merge, please, I also use the build script, and it does not work :c |
|
@black-rusuz you are the first person commenting on this PR since its creation over year ago. The maintainer hasn't commented or expressed interest in it, so I don't think it would be relevant for me to spend time resolving conflicts. |
|
@vkammerer Sounds logical, I didn't look at the publication date... Although, I find it strange that the developers of such a popular package, which is obviously good for CI/CD, didn't take care of it. Btw, now I'm using icons_launcher |
|
@vkammerer apologies, I thought I had replied to this in the past, really appreciate this submission and definitely feel this is a good idea to include. I also love how you've included |
Hello and thank you for the library,
The function
createIconsFromArgumentsexposed inmain.dartreturns a Future, so users expect that the task will be fully done when the Future completes, but it currently isn't the case.How to reproduce
I noticed this because I am using the plugin in a dart CLI application, as one of our build steps. I am calling
exit(0)after the Future completes, which causes the plugin to not write images to disk.Cause
This bug is due to the fact that many Futures are currently not awaited, which is hard to spot because they are called from synchronous functions.
Fix
I have tried to spot all the Futures and to await them, but it could be that I forgot some.
I also added the unawaited_futures lint rule.
Tested
I have tested this change in our build process and it all works fine: images are written to disk when
createIconsFromArgumentscompletes.Caveat / Question
I wonder if this could affect the overall performance of the current implementation, since functions will be executed sequentially, while they are maybe executed concurrently in the current implementation?