-
-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix - fix markdown render in tools page #1351
Fix - fix markdown render in tools page #1351
Conversation
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1351 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 10 10
Lines 373 373
Branches 94 94
=========================================
Hits 373 373 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its getting difficult to differentiate between plain text and URL link, pls. fix them
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍🏻
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What kind of change does this PR introduce?
Bugfix: Ensures that tooling listing notes are processed as markdown.
Issue Number:
Screenshots/videos:
Screencast.from.2025-01-21.15-36-50.webm
If relevant, did you update the documentation?
No
Summary
This PR addresses the issue where tooling listing notes were not being processed as markdown. The raw markdown text was displayed instead of rendering correctly. The issue occurred due to a missing markdown parser in the rendering pipeline for these notes. The changes fix that
Does this PR introduce a breaking change?
No