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.
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
[docs] Update unstyled demos to not depend on
@material-ui/core
#26869[docs] Update unstyled demos to not depend on
@material-ui/core
#26869Changes from 4 commits
6b2887e
f70e232
e61fac5
5031898
35554f6
c2b7a41
d397f28
9c0e7c4
5d0313d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Why not keep the Stack? It's meant as a CSS helper. It might where the limit between
@material-ui/system
and@material-ui/core
is. Developers won't use it when they copy the demo.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.
The goal was to eliminate any dependency on
@material-ui/core
. Once we have a dedicated doc for the unstyled components I think it would be strange that we have the@material-ui/core
as a dependency here. Anyway, no strong opinion as as you mention it is a CSS helper, so I could revert this change.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.
Interesting problem, not sure what would be best, no objection to moving forward with your approach.
We could likely add the Stack back once migrated to the system?
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.
This makes sense 👍 will leave the comment open for reference, and will keep the demo without the
Stack
component for now.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.
What changed now? I remember also trying to remove unrelated components from demos and I think I was shut down.
To be clear: I'm very much in favor of removing unrelated components like Stack or Box because they make the learning curve steeper.
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.
Oops, the conversation got moved to #26869 (comment).