Require a fix name / error code
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 232
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Original issue: https://github.com/iisaduan/ts-fix/issues/15
@andrewbranch commented July 28, 2021
I think we should do away with the default of applying all available fixes. It’s bound to produce a ton of undesired changes.
@iisaduan commented Aug 13, 2021
Currently, behavior is fixes are only applied if at least one of errorCode or fixName is supplied. Otherwise process exits with warning. 26bb5c6
There could be other ways to handle the case where no fixes or errors are given, such as printing what errors and fixes are present
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 path that handles runs without an errorCode or fixName, using the current behavior and the linked original issue as context. Done requires an agreed behavior for the no-selection case—such as requiring a selector or listing available errors and fixes—and verification of that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100