Add AnalysisDriver.resetUriResolution() and use it for analysis.reanalyze request.
This CL changes "analysis.reanalyze" API. We decided to repurpose it. It was not used for some time now in IntelliJ, and AFAIK has never been used in VS Code. R=brianwilkerson@google.com, paulberry@google.com Change-Id: I7510b0189197c9f3f848b0fc59a7b2bd22889ac7 Reviewed-on: https://dart-review.googlesource.com/c/85523 Reviewed-by: Paul Berry <paulberry@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Konstantin Shcheglov <scheglov@google.com>
This commit is contained in:
committed by
commit-bot@chromium.org
parent
b72ca19f33
commit
3428cc6dae
@@ -167,18 +167,10 @@ public interface AnalysisServer {
|
||||
/**
|
||||
* {@code analysis.reanalyze}
|
||||
*
|
||||
* Force the re-analysis of everything contained in the specified analysis roots. This will cause
|
||||
* all previously computed analysis results to be discarded and recomputed, and will cause all
|
||||
* subscribed notifications to be re-sent.
|
||||
*
|
||||
* If no analysis roots are provided, then all current analysis roots will be re-analyzed. If an
|
||||
* empty list of analysis roots is provided, then nothing will be re-analyzed. If the list contains
|
||||
* one or more paths that are not currently analysis roots, then an error of type
|
||||
* INVALID_ANALYSIS_ROOT will be generated.
|
||||
*
|
||||
* @param roots A list of the analysis roots that are to be re-analyzed.
|
||||
* Force re-reading of all potentially changed files, re-resolving of all referenced URIs, and
|
||||
* corresponding re-analysis of everything affected in the current analysis roots.
|
||||
*/
|
||||
public void analysis_reanalyze(List<String> roots);
|
||||
public void analysis_reanalyze();
|
||||
|
||||
/**
|
||||
* {@code analysis.setAnalysisRoots}
|
||||
|
||||
Reference in New Issue
Block a user