Fix builder-styling locale MDX parse errors blocking production deploy#413
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
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.
Problem
The production deploy on
mainfails at the Check MDX parse gate (failed run): six auto-translated copies ofbuilder-styling.mdx(es, ja, ru, tr, vi, zh) fail with:Cause
The translation workflow dropped the blank line between the Visibility bullet list and the multi-line
<div style={{...}}>YouTube embed. Without the blank line, the JSX block is parsed as a lazy continuation of the last list item, and the unindented lines inside the{{...}}expression break the MDX parser.Fix
Re-insert the blank line in all six locale files, mirroring the English structure.
node scripts/check-mdx-parse.mjsnow passes: 4794 files parsed cleanly.🤖 Generated with Claude Code