Rethink sorting fixes by start
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 232
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the tool accepts all fixes that don't collide, and if there are colliding fixes, the tool then picks the fix that occurs first by start index. This however, can produce several unwanted effects in the resulting code, such as applying multiple fixes for one error, or prioritizing changes by how the code is organized, instead of which fix is most likely to be applied. As written in #5, this is already done by services, and could be used to improve the output of the tool.
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 reading issue #5 and the sorting behavior described here. Define how service-side prioritization should replace start-index ordering, then verify that colliding fixes avoid multiple fixes for one error while non-colliding fixes continue to apply.
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
- Mostly clear
- Newbie friendliness
- 25/100