microsoft / microsoft/lage

Allow CLI argument input from a file

Open
#315 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement needs RFC
Dominant language
TypeScript
Stars
816
Forks
88
PR merge metrics
No merged PRs in 30d

Description

Windows has 8191 character limit on the CLI argument length. This limit can be easily hit on CI systems for big monorepos where we want to give lage a list of packages using the to or scope arguments.

Since lage is using yargs-parser internally, we can easily add support for accepting a CLI argument, using the opts.config which would point to a configuration json file, which can be read by yargs-parser to get the CLI input. This configuration file option would of course be optional, and users should be able to pass CLI arguments normally using the CLI with the option to use the configuration file in case they need to bypass windows limits.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the CLI entry point and its yargs-parser integration. Check how the to and scope arguments are parsed, then verify that an optional configuration JSON file can supply CLI input while normal command-line arguments continue to work. Done means both input paths are supported without requiring the configuration file.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.