Fix MDX parse error in getting-group.mdx#4057
Open
mintlify[bot] wants to merge 2 commits intomainfrom
Open
Conversation
Generated-By: mintlify-agent
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
Escaped curly braces in
experiments/implementation/getting-group.mdxthat were causing an MDX parse error (Could not parse expression with acornat line 80).Broken links scan
mint broken-linksfound no broken links across the docs. All internal links resolve correctly.Fix applied
experiments/implementation/getting-group.mdx{group name},{override name}in a markdown table were interpreted as JSX expressions, causing a parse error that blocked validation\{group name\},\{override name\}Validation
mint broken-links— passes (no broken links)mint validate— the only error is a pre-existing 403 from an external OpenAPI URL fetch, unrelated to this change