Code analysis fails to get configured for non-open files the 1st time it's run #12313
Labels
bug
Feature: Code Analysis
Related to integration with clang-tidy, cppcheck, cl.exe /analyze, etc.
fixed
Check the Milestone for the release in which the fix is or will be available.
Language Service
regression
A bug that didn't exist in a previous release
Milestone
Do Run Code Analysis on All files in a project configured with a configuration provider.
Bug: The 1st time it's done, all the files are skipped because it thinks it doesn't have the configuration information. Using it a 2nd time and it'll work. We get the finishedRequestCustomConfig message before the didChangeCustomConfigurations message.
The text was updated successfully, but these errors were encountered: