Problem
`BookmarkStore` persists exclusively to `context.workspaceState` (README: "Persists per workspace"). Users who jump between several different multi-root workspaces (not just folders within one) can't carry a bookmark over, and there's no equivalent of VS Code's Settings Sync for this data.
Proposal
Investigate offering an opt-in "global" scope (backed by `context.globalState` and/or `vscode.ExtensionContext.globalState.setKeysForSync` so Settings Sync picks it up) alongside the existing per-workspace store — e.g. a per-bookmark or per-folder toggle, or a whole-extension setting that changes where new bookmarks are stored.
Notes
Larger design question — needs a decision on whether this is per-bookmark, per-folder, or all-or-nothing before implementation. Consider scoping down to "just use `globalState` + `setKeysForSync`" as the smallest useful version.
Problem
`BookmarkStore` persists exclusively to `context.workspaceState` (README: "Persists per workspace"). Users who jump between several different multi-root workspaces (not just folders within one) can't carry a bookmark over, and there's no equivalent of VS Code's Settings Sync for this data.
Proposal
Investigate offering an opt-in "global" scope (backed by `context.globalState` and/or `vscode.ExtensionContext.globalState.setKeysForSync` so Settings Sync picks it up) alongside the existing per-workspace store — e.g. a per-bookmark or per-folder toggle, or a whole-extension setting that changes where new bookmarks are stored.
Notes
Larger design question — needs a decision on whether this is per-bookmark, per-folder, or all-or-nothing before implementation. Consider scoping down to "just use `globalState` + `setKeysForSync`" as the smallest useful version.