feat: add vitepress-demo-plugin and modify document demo#455
Conversation
WalkthroughThe PR introduces vitepress-demo-plugin to the documentation site and migrates all demo embeddings from a custom markdown directive syntax ( Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
Tip Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs). Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@packages/docs/fluent-editor/.vitepress/config.ts`:
- Around line 104-109: Demo plugin uses process.env.VITEPRESS_BASE with a
hardcoded '/' fallback which mismatches the site base; update the
vitepressDemoPlugin codeTransformer to fall back to the same site base value
instead of '/' — reference the site base variable (the exported/configured base
used at top of this file) and use it in the replace call (i.e., replace the
hardcoded '/' fallback in process.env.VITEPRESS_BASE || '/' with the site base
variable) so vitepressDemoPlugin, codeTransformer and process.env.VITEPRESS_BASE
use a unified base.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: c2259b0c-7ada-4d78-aa33-63763bc10780
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (27)
packages/docs/fluent-editor/.vitepress/config.tspackages/docs/fluent-editor/docs/demo/add-toolbar-item.mdpackages/docs/fluent-editor/docs/demo/ai.mdpackages/docs/fluent-editor/docs/demo/basic-usage.mdpackages/docs/fluent-editor/docs/demo/code-block-highlight.mdpackages/docs/fluent-editor/docs/demo/collaborative-editing.mdpackages/docs/fluent-editor/docs/demo/counter.mdpackages/docs/fluent-editor/docs/demo/custom-toolbar.mdpackages/docs/fluent-editor/docs/demo/emoji.mdpackages/docs/fluent-editor/docs/demo/file-upload.mdpackages/docs/fluent-editor/docs/demo/flow-chart.mdpackages/docs/fluent-editor/docs/demo/format-painter.mdpackages/docs/fluent-editor/docs/demo/formula.mdpackages/docs/fluent-editor/docs/demo/get-content.mdpackages/docs/fluent-editor/docs/demo/header-list.mdpackages/docs/fluent-editor/docs/demo/i18n.mdpackages/docs/fluent-editor/docs/demo/image-tool.mdpackages/docs/fluent-editor/docs/demo/markdown.mdpackages/docs/fluent-editor/docs/demo/mention.mdpackages/docs/fluent-editor/docs/demo/mind-map.mdpackages/docs/fluent-editor/docs/demo/readonly.mdpackages/docs/fluent-editor/docs/demo/screenshot.mdpackages/docs/fluent-editor/docs/demo/set-content.mdpackages/docs/fluent-editor/docs/demo/shortcut-key.mdpackages/docs/fluent-editor/docs/demo/table-up.mdpackages/docs/fluent-editor/docs/demo/toolbar-tip.mdpackages/docs/package.json
|
@wuyiping0628 先试用一段时间,没问题的话可以新开一个PR把: |
PR
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information
Summary by CodeRabbit
Documentation
Chores