Skip to content

Use of tasks groups for workspace generators #29900

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

Tcharl
Copy link
Contributor

@Tcharl Tcharl commented Jun 26, 2025

Contributes a bit to #28235 by using tasks groups on workspace generators.
Next steps: use of template framework and workspace types to avoid generator being stateful

FYI, didn't modify any line of logic or object: just moved code into different functions (using the new APIs)


Please make sure the below checklist is followed for Pull Requests.

When you are still working on the PR, consider converting it to Draft (below reviewers) and adding skip-ci label, you can still see CI build result at your branch.

@Tcharl Tcharl changed the title Use of tasks groups for workspace types Use of tasks groups for workspace generators Jun 26, 2025
@Tcharl Tcharl requested a review from mshima June 28, 2025 11:59
@Tcharl
Copy link
Contributor Author

Tcharl commented Jun 28, 2025

Don't think the errors are due to the code modified: seems to be the node and npm package version downloaded by the frontend plugin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant