prettier / prettier/prettier-cli
Support setting plugins in config files and plugin options in CLI flags
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 43
- Forks
- 10
- Avg merge
- 18m
- Merged PRs (30d)
- 1
Description
Currently if plugins and their options are both defined in a config file the CLI works, if they are both defined via CLI flags it works, but if plugins are defined in config files and flags are defined via CLI flags then it doesn't work anymore because the CLI thinks those options are unrecognized.
The best option here is probably doing nothing until an unknown flag is passed and then paying the cost for the discovery of the configs files just to be sure about whether we need to throw an error or not.
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 the CLI's unknown-flag validation and configuration-file discovery paths; the issue does not name specific files or tests. Reproduce the mixed configuration/CLI case, then verify that plugin options from config files are accepted while unrelated unknown flags still produce errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100