Allow safe connector MDX formatting#80
Merged
Merged
Conversation
gontzess
marked this pull request as ready for review
May 19, 2026 00:35
johnallers
approved these changes
May 19, 2026
gontzess
force-pushed
the
gontzess/shared-mdx-validation-fixtures
branch
from
May 19, 2026 00:50
2b6abbc to
39c379b
Compare
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.
Why
Connector docs validation was flagging valid docs syntax, including comment-only MDX expressions, table
<br/>line breaks,CardGroup, and indented code placeholders. This keeps the PR check aligned with docs syntax we expect while preserving rejects for executable MDX and unsafe URLs.What this changes
<br/>elements, andCardGroup.Validation:
npm testintools/mdx-lint: 30 passed.Rollout: