feat(markdown): support kbd tag rendering - #4237
Open
heartacker wants to merge 2 commits into
Open
Conversation
Contributor
Author
|
@tcp404 PTAL, thanks! |
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull Request
Description
Add support for rendering
<kbd>tags in both chat messages and document preview markdown views.rehype-rawwithrehype-sanitizeallowing<kbd>while keeping malicious scripts/attributes stripped..markdown-shadow-body kbdand.aionui-markdown :where(kbd)with subtle borders, background, monospace typography, and light/dark theme adaptability.<kbd>tags are properly preserved in preview and default markdown pipelines.Related Issues
Type of Change
feat— New feature (non-breaking change which adds functionality)Atomic PR Checklist (Rule 1)
<type>(<scope>): <subject>(English)Local Checks (Rule 3)
bun run format— formatting passesbun run lint— no lint errors (skip if no.ts/.tsxchanged)bunx tsc --noEmit— no type errors (skip if no.ts/.tsxchanged)bunx vitest run— tests passbun run i18n:types+node scripts/check-i18n.js) — N/A (no user-facing text strings added)Runtime Verification