Repository navigation
fix: render tables in page previews - #216
Merged
Merged
Conversation
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.
Why
Markdown tables in knowledge-page previews appear as pipe-delimited paragraphs because the renderer does not recognize table syntax. Payment schedules and other structured content become difficult to read.
How
Use the maintained GFM table extensions from the remark ecosystem throughout page parsing, rendering, and public export. Render tables with shadcn/ui’s base-nova Table primitives and a Markdown adapter inside Context Use, reused by private previews and public pages. Horizontal scrolling is keyboard accessible. Table content remains available in excerpts and search, and public exports retain safe references without requiring inline styles.