Clarify markdown table renderer overrides#800
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Contributor
Contributor
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.
Summary
Why
The table renderer intentionally avoids custom element hosts between native table sections, rows, and cells so streamed rows stay attached to the same browser table. The docs now make the override boundary explicit for consumers.
Verification
npx nx test chat -- --runInBand markdown-table.component.spec.tsnpx nx lint chat --skip-nx-cachegit diff --checkNotes
npx nx lint websiteis currently blocked by unrelated generatedapps/website/public/demo/main.jslint errors on this checkout.npm run generate-agent-contextis not needed for this change; that script renders the public context templates, not markdown guide content.