LuckyWindsck ยท GitHub

Conversation

@LuckyWindsck

๐Ÿ”— Linked issue

Resolves #5813

โ“ Type of change

  • ๐Ÿ“– Documentation (updates to the documentation or readme)
  • ๐Ÿž Bug fix (a non-breaking change that fixes an issue)
  • ๐Ÿ‘Œ Enhancement (improving an existing functionality)
  • โœจ New feature (a non-breaking change that adds functionality)
  • ๐Ÿงน Chore (updates to the build process or auxiliary tools and libraries)
  • โš ๏ธ Breaking change (fix or feature that would cause existing functionality to change)

๐Ÿ“š Description

  • Fix the problematic Markdown rendering by proper escaping backticks with the double backticks syntax.
  • I've also checked all occurrences of parseMarkdown to make sure that only <HighlightInlineType /> needs to fix.
  • I didn't check all component pages, but I don't think that this markdown change will break rendering.

Screenshot

Before After
image image

๐Ÿ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@LuckyWindsck

@vercel

@benjamincanac benjamincanac changed the title fix(docs): fix prop type rendering by properly escaping markdown docs(components): properly escape markdown in prop type rendering

Jan 5, 2026

benjamincanac

@benjamincanac

Read the original on github.com โ†—