-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
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
[core] Convert the waterfall module to an internal package #35323
Conversation
|
7efc6fd
to
e40b9c9
Compare
packages/waterfall/package.json
Outdated
@@ -0,0 +1,7 @@ | |||
{ | |||
"name": "@mui-internal/waterfall", |
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.
"name": "@mui-internal/waterfall", | |
"name": "@mui/internal-waterfall", |
Would this be better? To have the same org name
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.
Sure, I'm OK with both.
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.
There are other packages that use the @mui-internal scope. I'll rename them in a separate PR.
@@ -0,0 +1,7 @@ | |||
{ | |||
"name": "@mui/internal-waterfall", | |||
"version": "1.0.0", |
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.
Usually we use "5.0.0" for the private packages, but we can do the change once for all packages in a follow up PR.
This is a part of the scripts cleanup.
This PR moves the content of
/modules/waterfall
to/packages/waterfall
and creates an internal@mui/internal-waterfall
package out of it.It removes the top level
modules
directory and simplifies a few imports.