flutter / flutter/devtools

Property editor refactors do not highlight expected code after wrap

Open
#9,222 0 comments 0 reactions 0 assignees View on GitHub
P2 property editor
Dominant language
Dart
Stars
1.7k
Forks
404
Avg merge
6d 17h
Merged PRs (30d)
18

Description

Triggering refactor from code editor (expected behavior):

![Image](https://github.com/user-attachments/assets/8f0c94c4-3564-4a5d-bfa6-c2ff7c1d3d82)

Triggering refactor from property editor:

![Image](https://github.com/user-attachments/assets/e625ae14-2057-4f47-99a1-316406e0db48)

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

Open the contributing 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.