fix: red syntax highlighting on Node crawl response example#1043
Open
RichardBray wants to merge 1 commit into
Open
fix: red syntax highlighting on Node crawl response example#1043RichardBray wants to merge 1 commit into
RichardBray wants to merge 1 commit into
Conversation
The Node SDK crawl response snippet is a JS object literal (unquoted keys, template literals, [Object]), but was fenced as ```json. The JSON grammar can't parse it, so the highlighter rendered most tokens as errors (red) on /features/crawl. Tag it as js instead. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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
The Node SDK crawl response snippet on /features/crawl rendered almost entirely red. The snippet is a JavaScript object literal (unquoted keys, template literals,
[Object], bare...) but was fenced as ````json```, so the JSON grammar marked nearly every token as invalid.Changed the fence from
json Node``` tojs Node``` in:snippets/v2/crawl/sdk-example/js-response.mdxsnippets/v1/crawl/sdk-example/js-response.mdxSwept all base snippet dirs for other ````json``` fences with non-JSON content — these were the only two.
Before / After
🤖 Generated with Claude Code