Intellisense not working inside some folders
See original GitHub issueDescribe the bug
When editing files under a different folder like integration_tests
the linter doesn’t work. It works only under test/
and lib/
folders.
As you can see in the screenshot, the FlutterDriver
object has a dynamic
type instead of its real one.
Please complete the following information:
- Operating System and version: Monterey 12.3.1
- VS Code version: 1.67.1
- Dart extension version: 3.40.0
- Dart/Flutter SDK version: Flutter 3.0.0 - Dart 2.17.0
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Intellisense in not working on multiple folder structure #4630
As far as I can see, code analysis only works for 1 of the several roots I have in my workspace. The way...
Read more >Intellisense not working propeerly with "Open Folder" C++ ...
Ok hello again. I have done some more digging and intellisense is actually working it just isn't reading the header files properly. For...
Read more >VSCode doesn't do intellisense for classes in different root folder
You can easily check which jsconfig a file belongs to by running the JavaScript: Go to Project Configuration command in VS Code.
Read more >Visual Studio IntelliSense Not Working? What To Do.
Workaround #1: Restart Visual Studio But it's surprising (or maybe not) the number of times restarting Visual Studio manages to make it stop ......
Read more >IntelliSense not working in VS Code - The Windows Club
If IntelliSense or Autocomplete is not working in Visual Studio Code on your computer, the recommended fixes in this post are sure to...
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
Ah, glad you found it. I believe that’s expected behaviour - the files need to be analysed to provide some of this functionality.
Just found out that in my
analysis_options.yaml
I had:Removing the line
- "integration_test/**/*.dart"
solves the issue