Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat: removecss from variouscomponents/ elements#21263

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
jakehwll wants to merge12 commits intomain
base:main
Choose a base branch
Loading
fromjakehwll/mui-cssnuke-components

Conversation

@jakehwll
Copy link
Contributor

@jakehwlljakehwll commentedDec 14, 2025
edited
Loading

This attempts to remove all of the MUI/@emotion basedcss props. We've begun by doing this specifically in thecomponents/ folder. This should serve to align ourselves better with Tailwind/shadcn and our goal to remove mui from the database.

I've made attempts to ensure theline-height is consistent, however this isn't always in best-practice with Tailwind in some cases. Minor pixel shifts may happen. There are around 9 or so components living incomponents/ I haven't updated yet as the logic was scarier to migrate away from MUI.

Note

This pull-request is a fork-out of#21154 as I found it was getting too big to merge and hard to understand. Alongside this various components were being misrepresented in Chromatic (despite rendering fine in Storybook). I felt it better to make this a set of PRs.

@codex

chatgpt-codex-connector[bot] reacted with thumbs up emoji
Comment on lines +55 to +59
exportconstEnterprise:Story={
args:{
children:<EnterpriseBadge/>,
},
};
Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This lacked a story and therefore lacked coverage. I introduced this test here.

Comment on lines +75 to +79
exportconstDeprecated:Story={
args:{
children:<DeprecatedBadge/>,
},
};
Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Ditto

This lacked a story and therefore lacked coverage. I introduced this test here.

color:theme.roles.warning.text,
}),
}satisfiesRecord<string,Interpolation<Theme>>;
constbadgeClasses={
Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Not sure if we want to do this as apart of this PR but this probably could be better served byclass-variance-authority.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This entire component had no tests, I've introduced some so we can catch any issues going-forward with MaterialUI being removed.

<FormSection
classes={{
root:"flex flex-col gap-4",
root:"flex flex-collg:flex-col gap-4 lg:gap-4",
Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This is necessary due to new breakpoints being in Tailwind now. I don't love it..

@jakehwlljakehwll marked this pull request as ready for reviewDecember 14, 2025 15:35
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@aslilacaslilacAwaiting requested review from aslilac

@jaaydenhjaaydenhAwaiting requested review from jaaydenh

At least 1 approving review is required to merge this pull request.

Assignees

@jakehwlljakehwll

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@jakehwll

[8]ページ先頭

©2009-2025 Movatter.jp