-
Notifications
You must be signed in to change notification settings - Fork 27k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated with-mdx-remote dynamic components example #25366
Conversation
Fixed the missing prop 'components' to <MDXRemote /> and added a defaultComponent and source mdx to provide clarity on the example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Hi @timneutkens Due to the Lint issue, I have updated the branch by running prettier, can you please review it? Thank you :) |
Hey Awesome people! I am waiting for approval to push this change 😀 |
@payapula please don't directly tag people like that 🙏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Sorry, I thought this was missed. |
- Fixed the missing prop `components` to `<MDXRemote/>`. - Added a `defaultComponents` and `source` mdx to provide more clarity on the example. ## Documentation / Examples - [x] Make sure the linting passes
components
to<MDXRemote/>
.defaultComponents
andsource
mdx to provide more clarity on the example.Documentation / Examples