fix: merge duplicate markdown_extensions keys in mkdocs.yml - #709
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe MkDocs configuration moves the Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The MkDocs configuration change is low risk and documentation builds confirm the Mermaid setup works as intended. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
Fix
Merged both blocks into a single `markdown_extensions` key, preserving the `pymdownx.superfences` mermaid config unchanged.
Verification
Built the docs with `mkdocs build` before and after the change and counted `headerlink" anchors in the output:
Confirmed all 6 extensions (`abbr`, `admonition`, `attr_list`, `def_list`, `toc`, `pymdownx.superfences`) load correctly and the mermaid `custom_fences` config is preserved verbatim.