2 Commits (feat/scoped-shiki-options)

Author	SHA1	Message	Date
Divyansh Singh	b2060d5d3c	feat(markdown)!: scope shiki options under `markdown.shiki` ... Shiki-specific markdown options now live in a single `shiki` option whose fields follow shiki's own naming where they map directly. `ShikiOptions` and `ThemeOptions` are defined in and exported from the highlight plugin, like the other markdown plugin option types. Also hardens the highlighting pipeline while moving it: - `theme`/`defaultLang`/`transformers` resolve with `??`, so plain-JS configs passing `null` still get the defaults - the unknown-language fallback now loads `defaultLang` through the same guarded path and degrades to `txt` if the configured default itself cannot load - `defaultLang` is typed `StringLiteralUnion<BuiltinLanguage | SpecialLanguage>` for autocompletion, matching how shiki types `lang` BREAKING CHANGE: the top-level shiki-related markdown options were removed in favor of `markdown.shiki.*`: - `markdown.theme` -> `markdown.shiki.theme` - `markdown.languages` -> `markdown.shiki.langs` - `markdown.languageAlias` -> `markdown.shiki.langAlias` - `markdown.defaultHighlightLang` -> `markdown.shiki.defaultLang` - `markdown.codeTransformers` -> `markdown.shiki.transformers` - `markdown.colorReplacements` -> `markdown.shiki.colorReplacements` - `markdown.shikiSetup` -> `markdown.shiki.setup` Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	3 weeks ago
Divyansh Singh	fccc617102	feat(markdown): expose Shiki color replacements in markdown options (#5153)	6 months ago