dart-sdk/pkg/analysis_server
Danny Tuppeny 1861eac395 [analysis_server] Fix an edit conflict renaming folders containing files that reference siblings
Renaming a folder with files that referenced each other would fail with edit conflicts. The pass over the first file would update the reference to the other (going from "a.dart" to "../old/a.dart" as if the other file wasn't moving too) and then then when processing the second file, it would try to update the import back.

It doesn't seem to ever make sense to update relative paths when the "other" file is also in the folder being renamed, so this skips them.

Change-Id: I14c09977aa66017eecac5922d0e3caacf59350fb
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/247541
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
Commit-Queue: Brian Wilkerson <brianwilkerson@google.com>
2022-06-08 14:07:25 +00:00
..
benchmark Satisfy library_private_types_in_public_api in analyzer 2022-05-22 01:45:33 +00:00
bin [analysis_server] re-enble null safety for the analysis server entrypoint 2021-05-13 17:18:15 +00:00
doc [analysis_server] Set Container() as final tabstop/selection in Flutter snippets 2022-05-25 18:57:28 +00:00
lib [analysis_server] Fix an edit conflict renaming folders containing files that reference siblings 2022-06-08 14:07:25 +00:00
test [analysis_server] Fix an edit conflict renaming folders containing files that reference siblings 2022-06-08 14:07:25 +00:00
tool [analysis_server] Improve naming of LSP codegen types 2022-06-06 19:53:48 +00:00
analysis_options.yaml Satisfy library_private_types_in_public_api in analyzer 2022-05-22 01:45:33 +00:00
AUTHORS
CHANGELOG.md
CONTRIBUTING.md
LICENSE Update LICENSE 2021-04-07 10:28:38 +00:00
OWNERS [infra] Add OWNERS to the Dart SDK 2022-02-14 14:06:34 +00:00
pubspec.yaml [pkg] prefer 'any' deps for package dev dependencies 2022-05-27 01:34:59 +00:00
README.md "master->main" migration 2021-09-09 18:14:36 +00:00

analysis_server

A long-running process that provides analysis results to other tools.

The analysis server is designed to provide on-going analysis of one or more code bases as those code bases are changing.

Using the server

The analysis server is not intended to be used stand-alone, and therefore does not have a human-friendly user interface.

Clients (typically tools, such as an editor) are expected to run the analysis server in a separate process and communicate with it using a JSON protocol. The original protocol is specified in the file analysis_server/doc/api.html and Language Server Protocol support is documented in tool/lsp_spec/README.md.

Features and bugs

Please file feature requests and bugs at the issue tracker.