Dart-Code: Do not start the Dart analysis server from the root if Dart projects are in subfolders
This plugin always runs the analysis server from the root, resulting in a never terminating or hanging analysis in the dart-sdk. This is because the analyzer does not support analysis from the root of the dart-sdk project.
@dcharkes, thanks for the report! Generally, the use case of starting the analysis server from the root of the sdk is not supported.
@sjindel-google mentioned the Emacs plugin does not have the same issue, because it uses the .packages
or pubspec.yaml
files to determine from which folder to start analysis.
Would it be possible to get this behaviour in the VSCode plugin?
How to reproduce
- clone https://github.com/dart-lang/sdk
- open VSCode
- open the root folder of dart-lang/sdk
- enable Dart Code plugin
Analysis does not terminate, and generates 10000+ errors.
Expected behaviour
Analysis terminates normally (with a bunch of errors, as this is not a normal Dart project).
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 27 (7 by maintainers)
I don’t actually control the scheduling of analyzer issues, so I can’t say for sure. I think it’s worth opening an issue so that, if nothing else, we have some history in a place where we might be able to find it.