Clarify React component import limitations in MDX #3105
Merged
+4
−0
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.
Added clarification that nested React component imports aren't supported in MDX files. All components referenced in JSX must be imported directly into the parent MDX page.
Files changed:
Created by Mintlify agent
Note
Low Risk
Documentation-only change that adds guidance; no runtime or behavior changes.
Overview
Clarifies MDX React component usage by adding a
Notestating that nested component imports are not supported.Documentation now instructs that if a React component depends on other components, all of them must be imported directly in the parent MDX file (rather than importing within snippet/component files).
Written by Cursor Bugbot for commit ae84f75. This will update automatically on new commits. Configure here.