refactor: club all the custom MDX Components inside mdxCompenents directory#7817
Open
TusharThakur04 wants to merge 1 commit intowebpack:mainfrom
Open
refactor: club all the custom MDX Components inside mdxCompenents directory#7817TusharThakur04 wants to merge 1 commit intowebpack:mainfrom
TusharThakur04 wants to merge 1 commit intowebpack:mainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
@evenstensberg review please. |
TusharThakur04
force-pushed
the
refactor/club-mdx-components
branch
from
15a7457 to
1baf577
Compare
Contributor
Author
|
@ovflowd branch had merge conflicts, resolved now. |
ovflowd
approved these changes
Feb 15, 2026
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
2 participants
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
This PR clubs the custom MDX Components inside the
mdxComponentsdirectory for better structuringWhat kind of change does this PR introduce?
refactor
Did you add tests for your changes?
no
Does this PR introduce a breaking change?
no
If relevant, what needs to be documented once your changes are merged or what have you already documented?