Dart analyser need to be manually run too often
See original GitHub issueeach time I’m running flutter pub pub run build_runner build --delete-conflicting-outputs
(or whatch equivalent) the IDE doesn’t get what as been updated so I need to manually run the dart analyzer for the changes to be taken into consideration. Same when I flutter packages get
I need to run the dart analyzer for the changes to be in the IDE.
Would be nice to run dart analyzer automatically on package get (or having a checkbox on settings to enable that). For the build_runner I don’t have any solution except implementing #3137 that will allow the IDE to run dart analyzer when needed.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Customizing static analysis - Dart
This document explains how to customize the behavior of the analyzer using either an analysis options file or comments in Dart source code....
Read more >Dart Analyzer performance + IDE = Duration(seconds
I've cleared and cleaned and restarted everything so many times my computer has started to ask if _I'm_ ok. The basic gist is...
Read more >Dart Analyzer terminated on flutter clean or flutter run
I am on the latest VS Code version. so the Dart analyser must be stopping when your CPU Usage reaches 100% or near...
Read more >Analyze & improve Flutter code quality - YouTube
Dart Code Metrics is a static analysis tool that helps you analyze and improve your code quality.It collects analytical data on the code ......
Read more >analyzer | Dart Package - Pub.dev
Integrators that want to add Dart support to their editor should use the Dart Analysis Server. The Analysis Server API Specification is available....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes that why I mention it because I think the problem might be here. Excluded in the sens that they are under my
.gitignore
as I don’t want then in versioning control. I tried to remove them from it but no more luck…But I think I found the problem ! On my analysis_options I have this:
Meaning that I don’t want to have lint for generated file as they don’t follow my conventions. But by doing that the analysis server is totally ignoring my changes ! I tried to remove the exclude rules and then it works ! So not sure if it’s a problem on the plugin or on the analysis server 😕 but at least we know the reasons ^^
Glad you tracked down the problem.
@bwilkerson Is there a way for generated files to be treated differently from source files by the analyzer? It sounds like he wants the files to be analyzed but not to have any problems listed in the problems view.