Skip to content

Adding ResolvedLibraryResult and ResolvedUnitResult to all our RefactoringImpl classes #61695

@FMorschel

Description

@FMorschel

Based on #57092, I'm proposing we also add both ResolvedLibraryResult and ResolvedUnitResult to all our RefactoringImpl classes.

This will help us with some processing without the need to use the SearchEngine for some easier refactorings (like #57031). And since for most of the current Refactors we already provide a ResolvedUnitResult, we already have the ResolvedLibraryResult handy.

I've opened https://dart-review.googlesource.com/c/sdk/+/453845 for this change.

I'll add you, @srawlins and @bwilkerson as reviewers. Tagging you both here so we can discuss this (if you disagree for any reason).

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-devexpFor issues related to the analysis server, IDE support, linter, `dart fix`, and diagnostic messages.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions