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

feat: ensure e2e projects have implicitDependencies declared #55

Open
1 task
getlarge opened this issue Oct 14, 2024 · 0 comments
Open
1 task

feat: ensure e2e projects have implicitDependencies declared #55

getlarge opened this issue Oct 14, 2024 · 0 comments

Comments

@getlarge
Copy link
Collaborator

User story

When using the plugin, the e2e project (envProject) should have implicitDependencies declared where (at least) the project being tested is listed.
This is a requirement to detect which files to use as cache inputs.

Acceptance criteria

  • Add an e2e test with a project that has empty implicit dependencies and watch the plugin failing|skipping.

Implementation details

In #48, I added a warning when implicitDependencies are empty, we could go further and skip the target's generation.

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

No branches or pull requests

1 participant