-
Notifications
You must be signed in to change notification settings - Fork 36
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
Fix return Promises so each step runs in sequence #11
base: master
Are you sure you want to change the base?
Conversation
Return the Promise of each executeCommand() call to PromiseSeries, so that commands are executed in sequence, not in parallel.
+1 |
please merge this. this extension is pretty much broken without this. |
@Spongman Indeed |
also, the 'custom delay' patch is unnecessary with this patch. |
why is it not in...? |
Is this extension abandoned? This fix is pretty core, why no merge? |
This worked well for me and is easy to understand. Simply add Current: Line 34 in 96b0d7b
Line 38 in 96b0d7b
Fixed: Line 34 in de2633d
Line 38 in de2633d
|
Since it's been three years with no merge I found this fork that fixes this: https://github.com/ctf0/macros |
@geddski how is it about this Pull Request? Can we may work on this this weekend and merge and release a version 1.3? |
I also am affected by the issue. See https://stackoverflow.com/questions/72153504/prevent-asynchronous-order-of-command-sequence-execution-in-vs-codium I added these two |
@jpotterm How to install that? It seems it has not been published in marketplace? |
Return the Promise of each executeCommand() call to PromiseSeries, so that commands are executed in sequence, not in parallel.