Skip to content
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

Reference sub-tasks in multi-root workspaces #84800

Closed
felwolff opened this issue Nov 14, 2019 · 5 comments
Closed

Reference sub-tasks in multi-root workspaces #84800

felwolff opened this issue Nov 14, 2019 · 5 comments
Assignees
Labels
feature-request Request for new features or functionality tasks Task system issues

Comments

@felwolff
Copy link

If I define a workspace wide task, I would like to specify that it depends on tasks defined in the tasks.json files of the folders inside the workspace. Example: I develop a program and a library, which is used by the program, inside the same workspace. Now I want to build the program and specify that the library must be built first. I have build tasks for both inside their respective tasks.json files, but I cannot make one depend on the other.

One possibility would be to have a build-all tasks in .code-workspace that depends on those sub tasks and it should resolve the sub-task names just like it resolves launch names of sub-launch files.

Also see this Stackoverflow post.

@eternalphane
Copy link
Contributor

I do agree with @alexr00 that a task defined in one folder should not be referenced in another folder (#83065 (comment)). However, since workspace is used to manage folders, I think it reasonable to allow task in folders to be referenced in .code-workspace (and maybe vice versa).

@alexr00 alexr00 added feature-request Request for new features or functionality tasks Task system issues labels Nov 15, 2019
@alexr00 alexr00 added this to the Backlog Candidates milestone Nov 15, 2019
@vscodebot
Copy link

vscodebot bot commented Jan 15, 2020

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vscodebot
Copy link

vscodebot bot commented Mar 6, 2020

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding

1 similar comment
@vscodebot
Copy link

vscodebot bot commented Mar 6, 2020

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding

@vscodebot
Copy link

vscodebot bot commented Mar 16, 2020

🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Mar 16, 2020
@github-actions github-actions bot locked and limited conversation to collaborators May 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality tasks Task system issues
Projects
None yet
Development

No branches or pull requests

3 participants