docs

Advanced Usage

Advanced pages explain the boundaries you may need when configuring, integrating, or troubleshooting Flavor Grenade.

Where to go next

These pages are for readers who need more than the happy path: Configuration model details, Vault mode and single-file mode, Indexing and performance, Unsupported URI schemes, Opaque regions, and direct language-server integration.

Each article explains the boundary in plain English first, then gives a small example you can check in a vault.

Configuration Model Understand VS Code settings, vault markers, document extensions, and server options.Vault Mode and Single-file Mode Compare vault-wide behavior with the conservative single-file fallback mode.Indexing and Performance Learn how scanning, parsing, ignore rules, watchers, and rebuilds affect vault features.Unsupported URI Schemes and Confinement See how local vault targets are separated from external URLs, schemes, and outside paths.Parser Boundaries and Opaque Regions Review parser ordering, opaque-region marking, token parsing, and conservative edge cases.Compatibility and Direct LSP Integration Use the supported VS Code extension path first; direct LSP clients own advanced setup.

Current behavior and planned behavior

Current behavior is strongest in the VS Code extension and local language server. The extension ships a bundled JavaScript server module, opens local file-system workspaces, and sends the server the active Markdown flavor state. Auto Detect uses project configuration first, then vault markers, then syntax and context inference, then CommonMark fallback.

When a page describes direct LSP clients, read it as integration guidance. The server speaks LSP over stdio, but non-VS-Code clients still own launch, root selection, transport, configuration payloads, and file watching.

Current behavior: VS Code extension, direct server use, vault-aware Markdown features, flavor-aware parsing, path and URI confinement, and CommonMark fallback for generic Markdown.
Planned behavior: deeper public docs and website publishing automation, including S3/OIDC-backed delivery where the project uses it.