7 Commits (0e50d756f5ea9ef5055b4eb157fbfd765bfeb478)

Author	SHA1	Message	Date
Divyansh Singh	c2be0bf936	feat(markdown): accept booleans for plugin options ... Plugin options that could be disabled with `false` (`attrs`, `emoji`, `tasklist`, `anchor`, `toc`, `image`, `component`) now also accept `true`, which - like leaving them unset - enables the plugin with its default options. Only object values are forwarded to the plugins. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 weeks ago
Divyansh Singh	97f87817ea	feat(markdown): support GitHub-style task lists ... Renders `- [ ] task` syntax via `@mdit/plugin-tasklist`, enabled by default and configurable through the new `tasklist` markdown option (set to `false` to disable). The default theme hides list markers for task items and pulls checkboxes into the list gutter, GitHub-style. close #413 close #1923 close #3648 close #5110 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 weeks ago
Divyansh Singh	18380b0eb7	feat(markdown)!: replace markdown-it-attrs with @mdit/plugin-attrs ... The `fence` rule is disabled by default, replacing the patch we carried to stop curly attributes from consuming code block meta (line highlighting etc.). Drops both attrs patches and `@types/markdown-it-attrs`. BREAKING CHANGE: `markdown.attrs` options are now typed by `@mdit/plugin-attrs`: `leftDelimiter`, `rightDelimiter`, and `allowedAttributes` are renamed to `left`, `right`, and `allowed`. A `rule` option is available for toggling individual attribute rules (VitePress disables `fence` by default). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 weeks ago
Divyansh Singh	7c09583eaa	test(markdown): cover attrs behavior before plugin migration ... Captures what the markdown-it-attrs patch enforces (curly attributes never consume fence info, preserving line-highlight syntax) plus the supported attribute placements, as a regression baseline. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 weeks ago
Divyansh Singh	85ede55fdb	test(markdown): cover attrs/anchor plugin order independence ... attrs registers its core rule at a fixed position (before linkify) while anchor pushes to the end of the chain, so user-defined ids from curly attributes win regardless of registration order. Remove the comment that claimed the order matters. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 weeks ago
Divyansh Singh	3514d82617	refactor(markdown): restructure options and plugin registration ... - group `MarkdownOptions` into sections by concern (general, syntax highlighting, code blocks, markdown extensions, vue integration) and rewrite the jsdocs with a consistent voice, documenting the previously undocumented `externalLinks` default and correcting the `container` description (label customization, not plugin pass-through) - register plugins in accurately-labeled groups (vitepress customizations, community plugins, mdit-vue plugins) and note the order-sensitive couplings inline (lineNumbers after preWrapper, anchor after attrs) - add a test for the `cjkFriendlyEmphasis` toggle Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 weeks ago
Divyansh Singh	b8d9c8f9a9	feat(markdown): support disabling built-in markdown plugins ... Allows custom themes to opt out of markup and behavior added on top of vanilla markdown rendering: - `anchor`, `emoji`, `toc`, `component`, `image` now also accept `false` - new `preWrapper` and `snippet` boolean options (default true) - `lineNumbers` is a no-op when `preWrapper` is disabled, as its markup depends on the wrapper close #4484 close #4556 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 weeks ago