Skip to content

fix: correct the VSCodium shared storage path #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Merrit merged 1 commit into from
Aug 3, 2026
Merged

fix: correct the VSCodium shared storage path #30

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion lib/database.dart
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,8 +50,16 @@ abstract class DatabaseFilePath {
'$_home/.vscode-shared/sharedStorage/state.vscdb';

/// The VSCodium version of VSCode (new shared storage location).
///
/// The folder name is not derived from the product name; it comes from the
/// `sharedDataFolderName` key in `product.json`, which is independent of
/// `dataFolderName`. VSCodium rebrands `dataFolderName` and
/// `serverDataFolderName` but leaves `sharedDataFolderName` at the
/// Code - OSS default, so its shared storage lives in `.vscode-oss-shared`.
///
/// https://github.com/microsoft/vscode/blob/849be60ee89e414165969291f77d98e6fcd6e3cf/product.json#L6
static String codiumShared =
'$_home/.vscodium-shared/sharedStorage/state.vscdb';
'$_home/.vscode-oss-shared/sharedStorage/state.vscdb';

/// Returns the database file path for [version], preferring the new shared
/// storage location when it exists and falling back to the legacy path for
Expand Down