Issue with lage config parsing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 816
- Forks
- 88
- PR merge metrics
- No merged PRs in 30d
Description
With the introduction of parsePipelineConfig there is an error introduced, the code expects specific package tasks to depend on individual package tasks, which might not always be the case, it can very well be a recursive dependency.
Example:
"package-1#bundle": ["^bundle", "build"]
Current expectation:
"package-1#bundle": ["package2#bundle", "package1#build"]
This prevents the upgradation to newer lage versions.
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 at parsePipelineConfig and reproduce the reported configuration examples, including the recursive dependency form. Trace where package task dependencies are validated or expanded. Done means valid recursive dependencies no longer require every task to be package-qualified and newer lage versions can accept the configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100