Provide more info to task-scheduler so it can generate more accurate package-task graphs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 816
- Forks
- 88
- PR merge metrics
- No merged PRs in 30d
Description
Currently lage only gives a package graph and task graph separately, so task-scheduler doesn't know when some packages do not contain the tasks in the package.json.
Because of how the final combined package-task is generated, we might over-aggressively run tasks because of this missing info.
For example, if A depends on B and B depends on C:
A -> B -> C
and if only C has the task of special-C-build, when this following is called:
lage special-C-build --scope A
Nothing should be run because "A" doesn't have that task. The expected result is that nothing is run.
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 with the task-scheduler inputs used by lage special-C-build --scope A and compare how the separate package graph and task graph are combined. Trace the A→B→C example to determine where missing task information is lost. Done means the scoped command runs nothing when only C defines special-C-build, with the expected graph behavior covered by verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100