Repository navigation
Fix wrapped quoted strings in page frontmatter (invalid YAML) - #366
Merged
Merged
Conversation
128 pages (15 English, 113 translated copies) had a quoted frontmatter value wrapped across a line break with the continuation at column 0, for example: keywords: ['migrate to ClickStack', 'ClickStack migration guide ', 'ClickStack migration from Elastic', ...] That is invalid YAML: a continuation line inside a block mapping must be indented. Astro's js-yaml frontmatter parser tolerated it, so the pages built, but the `yaml` package that @astrojs/markdown-satteri 0.4 uses via @astrojs/internal-helpers rejects it with "Missing closing 'quote", which blocks the Nimbus 0.18 upgrade (#365). Rejoin each wrapped string on one line. Values are unchanged apart from the fold itself: a line break becomes a space, and the blank line inside six system-table descriptions becomes a space, so those meta descriptions read as two sentences. Every repaired file was re-parsed with `yaml` and compared against the lenient js-yaml reading of the original. Translated copies are fixed the same way so the translations deployment keeps building; GeneralTranslation regenerates them from the fixed English source with the same result. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
🕵
|
clickgapai
pushed a commit
to clickgapai/ClickHouse
that referenced
this pull request
Oct 15, 2026
Join wrapped quoted frontmatter strings so strict YAML parsers accept all documentation pages. ClickHouse/mintlify-docs-dev#366
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
128 pages have a quoted frontmatter value wrapped across a line break with the continuation at column 0:
That is invalid YAML: a continuation line inside a block mapping must be indented. Astro's js-yaml frontmatter parser tolerates it, so these pages build today. The spec-strict
yamlpackage that@astrojs/markdown-satteri0.4 uses (via@astrojs/internal-helpers0.12) rejects it withMissing closing 'quote, which is the blocker for the Nimbus 0.18.1 upgrade in #365.This PR rejoins each wrapped string on one line. Nothing else changes.
English files:
Value changes
Only what the YAML fold itself implies: a line break inside the string becomes a single space. The six
system-tablesdescriptions also contained a blank line, which becomes a space, so their meta description reads as two sentences instead of two paragraphs. Every repaired file was re-parsed withyamland compared against the lenient js-yaml reading of the original with whitespace normalised; all 128 match.Translated copies
Edited mechanically with the same join, so the translations deployment keeps building once #365 lands. GeneralTranslation regenerates these from the fixed English source and produces the same result. Two French files needed a manual join (one has an ASCII apostrophe inside a double-quoted description, one is a double-quoted multi-line description).
Verification
.md/.mdxfiles under the content and locale trees parses withyaml2.9: 0 errors (was 128).system.azure_queue_lognow has<meta name="description" content="Contains log entries … engine. It is safe to truncate or drop this table at any time.">.Independent of #365 and safe to merge first; the current Mintlify and Nimbus 0.13.1 builds read the joined strings identically.
🤖 Generated with Claude Code