-
Notifications
You must be signed in to change notification settings - Fork 1.7k
UI sanity when dealing with configs #2324
Copy link
Copy link
Closed
Labels
Feature: Extension APILanguage ServicebugfixedCheck the Milestone for the release in which the fix is or will be available.Check the Milestone for the release in which the fix is or will be available.help wantedCan be fixed in the public (open source) repo.Can be fixed in the public (open source) repo.
Milestone
Metadata
Metadata
Assignees
Labels
Feature: Extension APILanguage ServicebugfixedCheck the Milestone for the release in which the fix is or will be available.Check the Milestone for the release in which the fix is or will be available.help wantedCan be fixed in the public (open source) repo.Can be fixed in the public (open source) repo.
Type
Fields
Give feedbackNo fields configured for issues without a type.
When opening a new folder, we have pop ups for enabling configProviders, compileCommands, as well as a "configure your includePath" pop up if
#includes are not resolved. Only one of these should show up at a time and the priority is configProvider > compileCommands > includePath.Since all three of these popups can happen any any given time depending on when they are activated, we may not be able to guarantee ordering, but we can at least block them while another one is presented. If compileCommands shows up before configProvider, then configProvider should show up after compileCommands is dismissed. But if configProvider pops up and is accepted, then neither compileCommands nor includePath should appear at all.