You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to have the list of .vscode/tasks.json on a section in the Side Bar, such as in the Test Explorer.
I'm currently using an extension that renders the tasks in the Status Bar, but it gets quite crowded quickly.
One other benefit of this would be the possibility to run tasks right from a "Play" button on the task line of the Task Explorer, similar to what currently happens with tests in the Test Explorer.
Maybe adding subfolders to gather each set of tasks would even be better; however, I guess this would mean changing the way the JSON is parsed by VSCode since one could define the folder as a list of tasks in the tasks.json itself.
The text was updated successfully, but these errors were encountered:
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Thanks @gjsjohnmurray for pointing to the proper issue. I tried to look for existing issues but, due to the huge amount of "tasks" labels I could not find that one. Any updates on that issue?
It would be great to have the list of .vscode/tasks.json on a section in the Side Bar, such as in the Test Explorer.
I'm currently using an extension that renders the tasks in the Status Bar, but it gets quite crowded quickly.
One other benefit of this would be the possibility to run tasks right from a "Play" button on the task line of the Task Explorer, similar to what currently happens with tests in the Test Explorer.
Maybe adding subfolders to gather each set of tasks would even be better; however, I guess this would mean changing the way the JSON is parsed by VSCode since one could define the folder as a list of tasks in the tasks.json itself.
The text was updated successfully, but these errors were encountered: