RobertCraigie / RobertCraigie/pyright-python
Use `--quiet` instead of `--silent`
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 277
- Forks
- 31
- Avg merge
- 4h 22m
- Merged PRs (30d)
- 3
Description
See this comment for context: https://github.com/microsoft/pyright/issues/3627#issuecomment-1168554138
Things to consider:
- Does
--quietmean that warnings for new npm versions are output?
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
Read the linked Pyright issue and inspect the wrapper's command-line argument handling for the existing --silent option. Confirm whether --quiet should replace it and how warnings for new npm versions should behave; done means the wrapper uses the agreed option and its behavior is covered by the relevant CLI checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100