Improve "closest node" logic in analyzer plugin
Open
Nobody has claimed this yet.
area-analyzer-plugin
- Dominant language
- Dart
- Stars
- 432
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Description
Transferred from https://github.com/Workiva/over_react_analyzer_plugin/issues/46
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 reading the transferred issue at Workiva/over_react_analyzer_plugin#46, since this issue contains no implementation details or file references. Identify the analyzer plugin entry point and existing coverage for closest-node selection, then establish the expected behavior and add tests demonstrating that the revised logic is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100