Skip to content

UI sanity when dealing with configs #2324

@bobbrow

Description

@bobbrow

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Feature: Extension APILanguage ServicebugfixedCheck the Milestone for the release in which the fix is or will be available.help wantedCan be fixed in the public (open source) repo.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions