You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Markdown and Charts expose a Start Discussion link even though Discussions are disabled on their GitHub repositories, so those links lead to unavailable pages.
Add an optional library capability and hide that action for those two libraries. Discord stays available, and all other libraries keep their existing Discussions action.
Validation: GitHub API confirms Discussions are disabled for both repositories. Earlier browser checks confirmed those pages retain Discord and Query retains both actions. Full pnpm test passed on the fix before updating to the current base. No new dependencies or network calls. CI passed on the updated base. A focused esbuild minification comparison against the parent commit found +36 raw / +12 gzip bytes in the library metadata module and +23 raw / +14 gzip bytes in the route module. These are isolated module measurements, not a full production bundle comparison. The runtime change is one boolean check, with no new dependency, loop or network request.
Summary by CodeRabbit
New Features
Framework documentation now hides the “Start Discussion” link for libraries that don’t support discussions. Discord links remain available.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.
📝 Walkthrough
The library type now supports an optional discussion availability flag. The charts and markdown library records disable discussions. The framework documentation page hides the Start Discussion link when the flag is false. The Discord link remains unconditional.
The unavailable discussion links are hidden for Markdown and Charts, while Discord and other libraries’ discussion links remain available. No material merge risk was identified.
Pre-merge checks · 3 · 2
Failed checks (2 warnings)
Check name
Status
Explanation
Resolution
Out of Scope Changes check
The change also sets hasDiscussions: false for Charts. Issue [#1194] covers the Markdown documentation destination and does not identify Charts. The shared capability and route condition support the…
Remove the Charts-specific hasDiscussions: false change, or link a separate issue that requires hiding the Charts Discussions action.
Docstring Coverage
Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 3 files.
Write docstrings for the functions missing them to satisfy the coverage threshold.
Passed checks (3 passed)
Check name
Status
Explanation
Linked Issues check
Issue [#1194] requires that the unavailable Markdown Discussions destination is addressed. The Markdown library record sets hasDiscussions to false. The framework route renders Start Discussion …
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title clearly and concisely describes the main change: hiding unavailable library Discussions links.
Full details: Out of Scope Changes check
Explanation
The change also sets hasDiscussions: false for Charts. Issue [#1194] covers the Markdown documentation destination and does not identify Charts. The shared capability and route condition support the Markdown fix, but the Charts metadata change addresses a separate library and is not required by the linked issue.
Fix all pre-merge checks with AI
✨ Finishing Touches 💡 1
📝 Generate docstrings 💡
Commit to this branch
Create a new PR
🧪 Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Markdown and Charts expose a Start Discussion link even though Discussions are disabled on their GitHub repositories, so those links lead to unavailable pages.
Add an optional library capability and hide that action for those two libraries. Discord stays available, and all other libraries keep their existing Discussions action.
Fixes #1194.
Validation: GitHub API confirms Discussions are disabled for both repositories. Earlier browser checks confirmed those pages retain Discord and Query retains both actions. Full
pnpm testpassed on the fix before updating to the current base. No new dependencies or network calls. CI passed on the updated base. A focused esbuild minification comparison against the parent commit found +36 raw / +12 gzip bytes in the library metadata module and +23 raw / +14 gzip bytes in the route module. These are isolated module measurements, not a full production bundle comparison. The runtime change is one boolean check, with no new dependency, loop or network request.Summary by CodeRabbit