Files

T

Konstantin Shcheglov a900531934 Don't read files in _isPackageReference() during MoveFileRefactoringImpl.

We regularly get FileSystemException(s) like:
at _PhysicalFile.readAsStringSync (physical_file_system.dart:184)
at _OverlayFile.readAsStringSync (overlay_file_system.dart:206)
at FileSource.contentsFromFile (source_resource.dart:68)
at FileSource.contents (source_resource.dart:55)
at MoveFileRefactoringImpl._isPackageReference (move_file.dart:183)

So, instead we could use already recorded source content from which
the element model was built.

Alternatively we could record different kinds of references into
the index, e.g. IS_REFERENCED_BY_PACKAGE_URI or IS_REFERENCED_BY.

Change-Id: Ic4aa839f706f37c9df2504f866dfca7c7581c347
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/212860
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
Commit-Queue: Konstantin Shcheglov <scheglov@google.com>

2021-09-09 15:32:03 +00:00

benchmark

[analysis_server/benchmark] Fix memory usage calculation to avoid double-counting.

2021-09-03 19:02:27 +00:00

bin

[analysis_server] re-enble null safety for the analysis server entrypoint

2021-05-13 17:18:15 +00:00

doc

Fix grammar in quick_fix.md

2021-09-07 18:58:54 +00:00

lib

Don't read files in _isPackageReference() during MoveFileRefactoringImpl.

2021-09-09 15:32:03 +00:00

test

Add a quick fix for ABSTRACT_CLASS_MEMBER

2021-09-08 22:30:12 +00:00

tool

analysis_server: migrate to Object.hash functions

2021-09-09 00:23:43 +00:00

analysis_options.yaml

enable depend_on_referenced_packages

2021-06-04 14:19:08 +00:00

AUTHORS

…

CHANGELOG.md

…

CONTRIBUTING.md

…

LICENSE

Update LICENSE

2021-04-07 10:28:38 +00:00

pubspec.yaml

analysis_server: migrate to Object.hash functions

2021-09-09 00:23:43 +00:00

README.md

Add an initial version of a 'dart language-server' command.

2021-01-06 18:14:51 +00:00

README.md

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.