Skip to content

Fix Remarks code blocks to use Prism syntax highlighting#69

Merged
kyleamueller merged 1 commit into
mainfrom
fix-remarks-code-highlighting
Apr 13, 2026
Merged

Fix Remarks code blocks to use Prism syntax highlighting#69
kyleamueller merged 1 commit into
mainfrom
fix-remarks-code-highlighting

Conversation

@kyleamueller
Copy link
Copy Markdown
Owner

Summary

  • Remarks fenced code blocks now use SyntaxBlock instead of plain <pre><code>
  • Code blocks in Remarks get Prism syntax highlighting with Power Query grammar
  • Copy button and function name auto-linking now work in Remarks code blocks
  • Defaults to powerquery language when no language is specified on the fence

Why

Code blocks in the Remarks section (e.g., "Typical usage patterns" on the Web.Contents page) rendered as unstyled monospace text without highlighting, copy buttons, or clickable function names — inconsistent with the Examples section below.

Pages/files affected

  • src/app/functions/[slug]/page.tsxrenderRemarks() code block handler

Test plan

  • Visit /functions/web-contents — verify the 3 code blocks under "Typical usage patterns" have syntax highlighting, copy buttons, and clickable function names
  • Check other function pages with Remarks code blocks render correctly

🤖 Generated with Claude Code

Replace plain <pre><code> rendering in renderRemarks with SyntaxBlock
so fenced code blocks in Remarks sections get the same syntax
highlighting, copy button, and function auto-linking as Examples.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Apr 13, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
pqm-guide Ready Ready Preview, Comment Apr 13, 2026 3:19pm

Request Review

@kyleamueller kyleamueller merged commit 62a1558 into main Apr 13, 2026
6 checks passed
@kyleamueller kyleamueller deleted the fix-remarks-code-highlighting branch April 13, 2026 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant