Property editor refactors do not highlight expected code after wrap
- Dominant language
- Dart
- Stars
- 1.7k
- Forks
- 404
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 18
Description
Triggering refactor from code editor (expected behavior):

Triggering refactor from property editor:

I would expect the refactors to behave in the same way as they do from my code editor. This applies to other refactors that perform a text highlight like Wrap with FutureBuilder, ValueListenableBuilder, etc.
Contributor guide
Research direction
Start at the property editor refactor entry point and compare its behavior with the corresponding code editor refactor flow. Check the text-highlighting behavior for Wrap with FutureBuilder and ValueListenableBuilder, then verify that property-editor refactors highlight the expected code consistently with code-editor refactors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, devtools, flutter
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100