Skip to content
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

93/mui5 #127

Closed
wants to merge 24 commits into from
Closed

93/mui5 #127

wants to merge 24 commits into from

Conversation

spaenleh
Copy link
Member

This PR is a first step towards moving graasp-ui to muiv5.

For the moment, all makeStyles calls have been substituted for the @mui/styles alternative. In the future, using the emotion alternative with styled and sx props. Should also make sure that everything works as expected in compose.

closes #93

@spaenleh spaenleh added the feature New feature or request label May 25, 2022
@spaenleh spaenleh requested a review from pyphilia May 25, 2022 21:32
@spaenleh spaenleh self-assigned this May 25, 2022
Copy link
Contributor

@pyphilia pyphilia left a comment

Choose a reason for hiding this comment

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

Thanks for the PR, maybe we should do it slowly to migrate everything correctly. I would suggest to keep this branch and use it in other projects but not actually merge it before it's complete (and with tests?) what do you think?

.eslintrc Show resolved Hide resolved
package.json Outdated
Comment on lines 69 to 70
"react": "18.1.0",
"react-dom": "18.1.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

Last time I've tried it was not possible to use react 18 with uppy (which is used to upload files). Is it still possible to use graasp-ui if we stay on react17? Or maybe we should tag the current version of ui and not update for compose.

Copy link
Member Author

Choose a reason for hiding this comment

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

It seems they fixed the problem see this pull-request in uppy repo with uppy@2.10.0.

Copy link
Contributor

Choose a reason for hiding this comment

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

I just tried, the issue is from react side, they do not support cjs, which is used by uppy. The fix looks pretty easy so I hope it will be merged soon.

package.json Outdated Show resolved Hide resolved
src/Card/CardHeader.tsx Outdated Show resolved Hide resolved
src/Collapse/Collapse.tsx Outdated Show resolved Hide resolved
src/DrawerHeader/DrawerHeader.tsx Outdated Show resolved Hide resolved
src/Main/Main.test.tsx Show resolved Hide resolved
src/Loader/Loader.tsx Outdated Show resolved Hide resolved
src/ItemFlag/FlagItemButton.tsx Outdated Show resolved Hide resolved
src/ItemFlag/FlagItemButton.tsx Outdated Show resolved Hide resolved
spaenleh added 13 commits June 3, 2022 15:16
# Conflicts:
#	.eslintrc
#	package.json
#	src/ItemFlag/FlagItemButton.tsx
#	src/Loader/Loader.tsx
#	src/Main/Main.tsx
#	src/itemLogin/ItemLoginAuthorization.test.tsx
#	src/itemLogin/ItemLoginAuthorization.tsx
#	src/items/FileItem.tsx
#	src/items/LinkItem.tsx
#	src/items/S3FileItem.tsx
#	src/types.ts
#	yarn.lock
@pyphilia pyphilia mentioned this pull request Sep 10, 2022
@pyphilia pyphilia closed this Oct 19, 2022
@spaenleh spaenleh deleted the 93/mui5 branch November 3, 2022 10:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

update to MUI v5
2 participants