Cross-project dependence
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 168
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Currently we don't support backtracking in targets or deps to reference paths outside of the folder with the chompfile.toml root. This makes it impossible to do mtime-based comparisons for operations outside of the chompfile therefore requiring cross-project tasks to be re-run everytime and instead require their own invalidations.
Just adding support for arbitrary backtracking in targets and dependencies might be a good start for cross-project validations.
Further support for building multi-chompfile graphs based on treating files as "belonging to" their parent chompfile might then further provide something like a monorepo support.
Worth fleshing this out further and carefully considering the consequences, but it could be worthwhile if there is interest.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how targets and dependencies in chompfile.toml resolve paths relative to the project root. Define the scope for arbitrary backtracking and decide whether multi-chompfile graph support is included; document the consequences and acceptance criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100