lage shouldn't forward all arguments to all running targets
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 816
- Forks
- 88
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Lage forwards all arguments to all targets and this can break some targets
To Reproduce
Steps to reproduce the behavior:
- Create a target using
tsc, let's call thatbuild - Run
lageto trigger thisbuildtarget with-- --foo=bar tscfails becauselageforwards--foo=bartotscwhich complains that--foois unknown argument
Expected behavior
It should be possible to define which arguments are forwarded to which targets
Environment/Troubleshooting
N/A
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 tracing how lage parses arguments after -- and forwards them to running targets. Reproduce the issue with a tsc build target and --foo=bar; done means arguments can be assigned to intended targets without being sent to targets that reject them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100