Fix mintlify validate errors#367
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughMultiple documentation files receive formatting updates to improve markdown and HTML rendering consistency. Changes include HTML-escaping special characters for safe rendering, wrapping type definitions in inline code, adjusting URL and string representations, and escaping delimiters. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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.
Pull request overview
This PR addresses mintlify validate failures by adjusting Markdown/MDX-unsafe syntax (e.g., raw <...> and {...} fragments) so documentation renders and validates correctly in Mintlify.
Changes:
- Escapes or code-wraps MDX-sensitive tokens like
<name>and{"file_path":to prevent parsing/validation errors. - Adjusts type formatting in a schema table to avoid
<...>being interpreted as HTML/JSX. - Tweaks external link formatting to avoid MDX autolink issues.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| teach-me/learner-profile.md | Escapes <-> sequence to avoid MDX/HTML parsing issues. |
| learn/phase-2-qa.md | Wraps a JSON fragment containing { in code formatting to avoid MDX expression parsing. |
| docs/lsp-integration.md | Wraps Record<string, string> in code formatting inside a table for safer rendering. |
| docs/features/pipes-and-lan.md | Escapes <name> placeholders in command references to avoid MDX/HTML parsing. |
| README_EN.md | Removes MDX-problematic <https://...> autolink formatting. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| /pipes select <name> — 选中某实例(消息会广播到它) | ||
| /pipes deselect <name> — 取消选中 |
There was a problem hiding this comment.
In this fenced code block, replacing placeholders with HTML entities (<name>) will typically render literally (as <name>) because code blocks don’t decode entities the same way normal Markdown text does. This makes the example harder to read/copy. Consider keeping the code block examples as /pipes select <name> and only escaping placeholders in non-code contexts (e.g., headings), or use inline code/backticks there to avoid MDX parsing.
| /pipes select <name> — 选中某实例(消息会广播到它) | |
| /pipes deselect <name> — 取消选中 | |
| /pipes select <name> — 选中某实例(消息会广播到它) | |
| /pipes deselect <name> — 取消选中 |
|
|
||
| - **Online docs (Mintlify)**: [ccb.agent-aura.top](https://ccb.agent-aura.top/) — source in [`docs/`](docs/), PR contributions welcome | ||
| - **DeepWiki**: <https://deepwiki.com/claude-code-best/claude-code> | ||
| - **DeepWiki**: https://deepwiki.com/claude-code-best/claude-code |
There was a problem hiding this comment.
To keep this as an explicit hyperlink across Markdown renderers (and consistent with README.md), consider using standard link syntax like [DeepWiki](https://deepwiki.com/claude-code-best/claude-code) rather than a bare URL. This also avoids the MDX/JSX ambiguity that the previous <...> autolink had.
| - **DeepWiki**: https://deepwiki.com/claude-code-best/claude-code | |
| - **DeepWiki**: [deepwiki.com/claude-code-best/claude-code](https://deepwiki.com/claude-code-best/claude-code) |
Summary by CodeRabbit