Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Do not start the Dart analysis server from the root if Dart projects are in subfolders
See original GitHub issueThis 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).
Issue Analytics
- State:
- Created 5 years ago
- Comments:27 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
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.
Ok thanks, I’ll close this and leave it to you two to decide if there should be an analyzer issue. Thanks!