Skip to content

Figure out and fix which Calva settings should be scoped, and how #2083

Open
@PEZ

Description

@PEZ

From:

I noticed a problem with this setting, as well as almost all Calva settings, when testing this PR. I tested in a workspace where I had several root folders. When I have set a default for auto-selecting project type, that was used regardless of which folder I was jacking in to. Because I had set it with the Workspace settings... Trying to set it on Folder settings didn't work because we lack "scope": "resource" on the settings objects in the manifest. What's more. Even when I added that it still didn't work! Because we don't read folder settings... We should fix this. Connect Sequences and a lot of other settings make sense to add here. I think maybe all settings deserve this treatment. CC: @bpringe @julienvincent

For Calva to properly support using Workspace Folders we need to support the user scoping settings to a particular folder. I don't know for which settings this wouldn't make sense.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions