Skip to content

Separate config for each workspace #31

@nbolton

Description

@nbolton

Switching between projects is a little bit clunky, since the sync data is only relevant to the last project that was used, and when sync data is received it's procesed for all open windows (what if you have different VSC instances open with different projects?)

Use the workspace ID/name, store the sync data against that, send it over the wire, and only handle sync data that matches the workspace name. We should also ask the intended project type, so that if there are problems on the other end (e.g. no CMake extension), then an error is shown rather than just skipping.

What if the workspaces have different names because the dev is a bit inconsitent with their workspaces across computers? Not everyone likes to sync their VS Code or even be consistent.

Related:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions