-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Clean task #5540
Clean task #5540
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
709e8cb
to
6339731
Compare
@@ -196,6 +196,8 @@ async function resolveUserConfig( | |||
tasks: config.tasks ?? [], | |||
paths: { | |||
root: projectRoot, | |||
cache: config.paths?.cache ?? "", // TODO: resolve cache path |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have a task to properly implement this resolution? Can you create one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe these things should be defined in hardhat
, not core
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's part of #5524, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kanej can you confirm?
This PR requires #5527
and #5517.The logic to create the
cache
andartifacts
paths is missing, as it's outside the scope of this issue. Because of this, the tests are somewhat "manual" – we handle the folders manually to simulate different scenarios. However, this should be acceptable.The build is currently failing because it needs PR #5517 and some additional code (e.g., adding thecache
andartifacts
properties inv-next/core/test/internal/hook-manager.ts
).The task might require additional steps, such as calling
artifacts.clearCache?.()
, which depends on how the new build system works.