Closed kiontupper closed 4 years ago
I cannot reproduce this bug. Can you provide your tasks.json?
If VSCode does interrupt the order of tasks for some reason, I think it can use the order of tasks.json instead of the order provided by vscode.tasks.fetchTasks. No need for a new parameter.
It happened to me with the same tasks.json above, just without the position fields and the tasks just run NPM scripts.
I pushed a commit 178f4b1f16b237555744e141ee27945552d857ed. Now it should use the order in tasks.json exactly, I think this should solve your problem.
I found that sometimes the order of the tasks shown can be inconsistent (at least in newer versions of VSCode), breaking the logical order of large, multi-step workflows.
I wanted this to beBuild , Prebuild , Deploy
This change is quite simple: it adds a
position
field to the status bar options. When the extension loads the tasks, it sorts them according to theposition
value, which defaults to0
.This allowed me to fix the mess
Which yields the following result:
Much better! 🎉
PS: I also bumped the version number to
0.3.7
.