feat(misc): remove generation of target defaults for atomized e2e tasks #30730
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current Behavior
A target default (
dependsOn: [^build]
) for atomized e2e tasks is always generated to work around a previous limitation where tasks couldn't depend on continuous tasks. That meant we couldn't add the dependency to the app's serve task and had to add it to the build task.With continuous tasks now working, that limitation no longer exists. We're now able to correctly infer the task dependency on the app's serve task, and therefore, we can and need to remove the generation of
dependsOn: [^build]
in target defaults so it doesn't override what the Cypress and Playwright plugins infers.Expected Behavior
A target default (
dependsOn: [^build]
) for atomized e2e tasks should not be generated. Instead, the Cypress and Playwright plugins will infer the correctdependsOn
for the task(s) run in the configured web server command.Related Issue(s)
Fixes #