analyzing takes for too long when writing any code in flutter !
See original GitHub issueDescribe the bug
i am on ubuntu 20.04 and iam using dart and flutter with vs code and whenever i ever write any complex code it starts analyzing and it does that like non-stop over and over again so i have to write the code in a pad or whatever and paste it in vscode which is inconvenient at all !
To Reproduce
Steps to reproduce the behavior:
just by writing any complex code like Stream<List<NewsModel>> newsStream
or using dartz
like this Future<Either<T1,T2>>
Expected behavior it is expected to compile and analyze it as fast as possible in every code i write . Screenshots
Versions :
- VS Code version: 1.57.1
- Dart extension version: 3.23.1
- Dart/Flutter SDK version: Dart : 2.13.1 /Flutter : 2.2.1
Issue Analytics
- State:
- Created 2 years ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
No results found
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
Can you reliably reproduce this? If so, can you try:
If there’s nothing sensitive in the log file, you can share it in a gist or email it to me at logs@dartcode.org. Otherwise, let me know and I can give you some instructions to find the useful parts from the log that might help understand what’s wrong.
There were some fixes in Flutter 2.2.2 that solve issues like this, however my understanding is that they only apply to macOS, so I don’t think it’s that - although it may be worth upgrading to that version just to be sure.
Thanks!
I’ve filed https://github.com/dart-lang/sdk/issues/46505 about this as this appears to be a parser issue. I’ll close this one in favour of there, as it’s not something that can be fixed in the VS Code extension. Thanks!