chore: rebuild docs frontend + vscode extension (v0.1.21)#543
Open
Muizzkolapo wants to merge 2 commits into
Open
chore: rebuild docs frontend + vscode extension (v0.1.21)#543Muizzkolapo wants to merge 2 commits into
Muizzkolapo wants to merge 2 commits into
Conversation
Docs frontend out/ was stale since v0.1.14 (May 2) — missing the markdown rendering fix from #540 (May 16). Rebuilt to include DataCard markdown support in the inspector.
Muizzkolapo
force-pushed
the
chore/rebuild-frontends
branch
from
d39322a to
99a68f0
Compare
…iteral text stripHtml collapsed <br> tags and whitespace, making HTML-containing strings appear short enough for the plain-text path. This caused literal <br> to display instead of line breaks. Now detect HTML in the raw value and route to renderMarkdown regardless of stripped length.
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
1 participant
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
out/— was stale since v0.1.14 (May 2), missing markdown rendering fix from fix: render long text fields as markdown in inspector #540 (May 16)What was stale
The
data-card.tsxmarkdown rendering change (#540) wasn't compiled into the static output. The inspector would show raw HTML tags instead of rendered markdown for long text fields.Verification
npm run buildin docs frontend — cleannpm run buildin vscode-extension — clean