Repository navigation
fix(compose): repair the reference pages and revert two wrong fixes - #103
Merged
Merged
Conversation
A generated table cell held `[{time:0,value:0},{time:1,value:1}]`; MDX reads a
bare `{...}` as a JSX expression, the page failed to parse, and Mintlify served
the section root as the body of all 24 child pages while reporting every deploy
a success. Generator fixed in rendobar/rendobar#798; these are the regenerated
pages.
Also reverts two changes I shipped on a wrong diagnosis: #101 (moving the
overview to index.mdx and dropping `root`, which cost the nav behaviour) and
#102 (a validator rule for a collision that was never the cause).
Adds `validate:build` = `mint validate`, the only check that sees a build
error, and the one that was missing.
a-essawy
added a commit
that referenced
this pull request
Sep 24, 2026
#103 fixed the MDX parse error and the children still served the section landing page. Two variables had changed together, so the brace fix never got a clean test against the nav shape. Braces stay fixed; the group drops `root` for `jobs/compose/index` as its first page, which is what storage/ and automation/ use and what resolves children correctly on the live site today. `/docs/jobs/compose` still serves the overview, so no inbound link moves.
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.
The compose section has been serving its landing page as the body of all 24 child pages since #100 merged. Root cause, found with
mint validate:A generated table cell contained
[{time:0,value:0},{time:1,value:1}]. MDX reads a bare{...}as a JSX expression. The generator escaped pipes but not braces (fixed upstream in rendobar/rendobar#798); these are the regenerated pages.Mintlify reported all three deploys a success, listed every page in the sitemap and llms.txt, and served the section root for each one.
llms-full.txtcarried none of the 93 video embeds.mint devdoes not reproduce it.Reverting two fixes I shipped on a wrong diagnosis
I read the symptom as a routing collision between
jobs/compose.mdxandjobs/compose/, and shipped two changes for it. Neither was the cause:jobs/compose/index.mdxand dropped the group'sroot. That cost the nav behaviourrootgave (clicking the Compose parent opens the overview, and a child holds its highlight). Restored, andmint validatepasses with it.<dir>.mdxbeside<dir>/. That rule encodes a cause that does not exist and would block the shapemint validatesays is fine. Removed.The check that would have caught it
validate:buildrunsmint validate. It is the only one of the six that sees a build error, and it is the one that was missing.