Skip to content

forc-pkg: provide a way to check if an entry in build plan should be invalidated or not #7142

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
kayagokalp opened this issue May 2, 2025 · 0 comments
Assignees
Labels
enhancement New feature or request forc-pkg Everything related to the `forc-pkg` crate. team:tooling Tooling Team

Comments

@kayagokalp
Copy link
Member

forc-pkg builds a build plan from lock file and manifest. If there is a mismatched between them, the lock file is generated from manifest file. This means if any registry, git or ipfs source target changes, the build plan is invalidated by forc-pkg automatically as the build plan is re-generated.

Now the issue is with path dependencies. If anything changes in the path dependency, this change is not reflected to the lock file or the manifest file. (imagine src/lib.sw changes a declaration etc). This is the correct behavior but we also want to be able to tell if we should be re-building or not, so we need a way to hold some context about each member of the build graph. Whether they changed something or not and expose this functionality from forc-pkg, so that things like lsp can use this information.

@kayagokalp kayagokalp added enhancement New feature or request forc-pkg Everything related to the `forc-pkg` crate. team:tooling Tooling Team labels May 2, 2025
@kayagokalp kayagokalp self-assigned this May 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request forc-pkg Everything related to the `forc-pkg` crate. team:tooling Tooling Team
Projects
None yet
Development

No branches or pull requests

1 participant