Open christian-bromann opened 2 years ago
We should leverage the VSCode task schema for defining them and the widgets basically reads and displays them.
Also we should add this as a new section into the tree viewer.
We should leverage the VSCode task schema for defining them and the widgets basically reads and displays them. Also we should add this as a new section into the tree viewer.
I like those two requirements, @christian-bromann. So in essence this is widget is actually a generic VS Code task runner showcased based on NPM scripts/tasks?
Also we should add this as a new section into the tree viewer.
I kind changed my mind on this one because tree viewer sections need to be defined within package.json
and therefor show up also in non NPM projects.
Also we should add this as a new section into the tree viewer.
I kind changed my mind on this one because tree viewer sections need to be defined within
package.json
and therefor show up also in non NPM projects.
Not sure I understand. If a tasks.json is defined the treeviewer could be totally agnostic from what context project is loaded, no?
If a tasks.json is defined the treeviewer could be totally agnostic from what context project is loaded, no?
Yeah. If a task.json
is defined.
Discovering a new project can be challenging, especially if the project specific tasks are unknown. We can help expose these NPM tasks by offering a widget that allows to add descriptions and titles to an NPM task to help developers better understand what they do and when to use that NPM task.
Requirements:
package.json
and offer to add them to the list