OpenLightingProject / OpenLightingProject/open-fixture-library
Normalize CLI options, switch to yargs
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 258
- Forks
- 100
- Avg merge
- 11h 52m
- Merged PRs (30d)
- 53
Description
Use the same command line parameters for similar functions (e.g. always --plugin / -p for fixture import, export, export test, etc.).
Also use minimist for main.js to set the port and dev server.
And in the same PR, we could switch from the (done separately)colors devDependency to chalk as it's more versatile and less confusing (colors vs. color vs. color-names).
Contributor guide
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 locating main.js and the CLI entry points for fixture import, export, and export test. Compare their current command-line parameters, then make equivalent operations use --plugin/-p and ensure main.js handles the port and dev-server options with the requested argument parser. Done means the affected commands accept consistent options and their existing behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100