chore(prettier): ignore ejected swizzles, not wrapped ones - #4617
Open
thetaPC wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
thetaPC
marked this pull request as ready for review
August 5, 2026 21:53
thetaPC
requested review from
OS-jacobbell and
ShaneK
and removed request for
OS-jacobbell
August 5, 2026 21:53
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.
Issue URL:
What is the current behavior?
src/theme/README.mdsays swizzled components should be added to the prettier ignore so they stay diffable against@docusaurus/theme-classic, but onlyDocItemandDocRootwere listed.What is the new behavior?
.prettierignorelists the seven ejected components. Wrapped components (using@theme-original) are our own code, so they keep repo formatting:DocSidebar,TOC,MDXComponents/index.tsx, andDocRoot/Layout/Main.Does this introduce a breaking change?
Other information
N/A