-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Setup material-ui tests #1641
Setup material-ui tests #1641
Conversation
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.
I did the same as this except for I pulled typings in and I found that the material-ui did not work
Building off of work done in #1606 and #1641. Update build and dev process and documentation (as discussed in #1630 (comment)). The developer will just need to run lerna bootstrap, run npm start from the package they are modifying, then run the playground from packages/playground to get a live-reloading playground. Fix deploy previews by configuring netlify so that it runs lerna bootstrap, thus linking the packages with the local changes in the PR, before building the playground. Export typings from @rjsf/core (fixes #1583) -- did this in this PR so that @rjsf/material-ui would work as well. Fix playground issues in which the material-ui playground did not use the right ObjectFieldTemplate or ArrayFieldTemplate. Fixes #1630 .
Can we get a release with these fixes soon? |
Soon! |
I really hope so, I've just reached the point where this is completely blocking me. Is there anyway I can help? Review a PR or something? |
Yes please, so that we may override |
Reasons for making this change
Add tests to the material-ui theme so that it can be released.
Also, update the docs to discuss the themes in more detail.
Finally, refactors utils to be exported from the default @rjsf/core package so that they are properly transpiled -- fixes #1655 (this had to be done in order to get material-ui tests to work, so that's why both are done in the same PR)
So, previously an import would look like this:
Now you would need to do this:
Related: #1561 #1585 -- we'd have to get the theme documentation in first before merging these two PRs.