config-directory-fallback-error
The distinct error thrown when an owned Obsidian instance booted a vault against a different config folder than the one requested through configDirectory — Obsidian rejected the override, or never saw it, and silently fell back to .obsidian.
The fallback is silent by construction (setConfigDir swaps an invalid value for the default without a word) and the resulting vault looks perfectly healthy: it opens, its layout is ready, and it reports success. What it does not have is the settings, enabled plugins, and workspace of the folder that was asked for — so a suite that verifies behaviour against a real vault’s plugin set would silently verify nothing. Hence a hard failure rather than a warning, and, unlike SilentAsarFallbackError, no knob to downgrade it: there is no version of this outcome worth continuing against.
Exported so callers of connectToCdp / the transport can instanceof-match this specific failure.
Classes
Section titled “Classes”| Class | Description |
|---|---|
| ConfigDirectoryFallbackError | Thrown when a booted owned instance reports a different app.vault.configDir than the requested ConfigDirectoryFallbackErrorConstructorParams.requestedConfigDirectory. Carries both folder names and the vault path so callers can instanceof-match and report which vault was opened wrongly. |
Interfaces
Section titled “Interfaces”| Interface | Description |
|---|---|
| ConfigDirectoryFallbackErrorConstructorParams | Parameters for the ConfigDirectoryFallbackError constructor. |