FuelLabs / FuelLabs/sway

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

Open
#7,142 0 comments 0 reactions 1 assignee Claimed by @kayagokalp View on GitHub
enhancement forc-pkg team:tooling
Dominant language
Rust
Stars
61.4k
Forks
5.4k
Avg merge
3h 33m
Merged PRs (30d)
4

Description

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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.