Create dart-lang/sdk issues for analyzer_plugin issues we've hit
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
- Plugin
AssistContributorisn't async - can we PR to update the implementation to matcg outAsyncAssistContributor - DartFileEditBuilder.format doesn't take project line length into account
- Plugin-manager project never gets recopied, makes local dev difficult, especially when you merge the bootstrap plugin packages
- Semi-related to elated: https://github.com/dart-lang/sdk/issues/35281
- Putting observatory link in CPU/Memory page isn't super discoverable; what about "Status"
- All files in project are not resolved by default, requiring you to manually schedule them
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
Review the five analyzer_plugin concerns listed in the issue, including AssistContributor async support, DartFileEditBuilder formatting, plugin-manager copying, observatory discoverability, and default file resolution. Check the related dart-lang/sdk issue and existing upstream issues first; done means the distinct requests are clarified and corresponding SDK issues are created or linked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100