Upgrade to mui v5, variant 1 (fixes #2555)

[heath-freenome]

Reasons for making this change

Fix #2555 by adding the mui-5 theme as follows:

• Updated core to add React 17 as a peer-dependency to support mui-5 which requires it
  • This required removing the create-react-ref library that didn't support React 17, updating the single usage of it in a test with React.createRef()
• Copied the material-ui theme then ran the mui v4->v5 over the source code
  • Cleaned up the imports structures of the code base
  • Change the use of Input with OutlinedInput to match the new default variant
  • Removed the TextFieldProps in favor of simply using the updated WidgetProps in may of the TextField based widgets
  • Made a few other smaller Typescript fixes to a few Widgets
  • Updated the tests snapshot, disabling one test that was failing (due to mui issue
  • Updated the mui-5/README.md, mui/screenshot/png and a few other theme related documentation files
• Added a new playground-r17 package that contains only the core and mui-5 themes
  • This required upgrading react-monoco-editor, monoco-editor and monaco-editor-webpack-plugin to versions that support React 17
  • Updated DemoFrame to use the @emotion/react CacheProvider to replace the older @material-ui/styles StylesProvider
  • NOTE: I am not sure how to update the main deployment system to integrate this with the main published playground
    • @epicface perhaps we can work together to figure this out?
    • In the meantime, developers can use this non-published playground to test with

Checklist

• I'm updating documentation
  • I've checked the rendering of the Markdown text I've added
• I'm adding or updating code
  • I've added and/or updated tests
  • I've updated docs if needed
  • I've updated the changelog with a description of the PR
• I'm adding a new feature
  • I've updated the playground with an example use of the feature

[epicfaace]

Thanks for the PR. How do you think we should handle adding more and more code per new theme / version of material ui? Perhaps we should retire old versions of material ui themes after a while?

I'm also wondering whether it makes sense to call it @rjsf/mui-5or instead just publish a breaking change for@rjsf/material-ui`

[heath-freenome]

I actually thought of a way to possibly have the material-ui theme support both, with two themes in one. I will play with it on Monday and see if my idea will work

…

On Fri, Nov 12, 2021 at 7:20 PM Ashwin Ramaswami ***@***.***> wrote: ***@***.**** commented on this pull request. Thanks for the PR. How do you think we should handle adding more and more code per new theme / version of material ui? Perhaps we should retire old versions of material ui themes after a while? I'm also wondering whether it makes sense to call it @rjsf/mui-5or instead just publish a breaking change ***@***.***/material-ui` — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2603 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMKJCZDCS3RTVQOGNHT36HDULXKOXANCNFSM5H6CR36Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

-- This e-mail is private and confidential and is for the addressee only. If misdirected, please notify us by telephone, confirming that it has been deleted from your system and any hard copies destroyed. You are strictly prohibited from using, printing, distributing or disseminating it or any information contained in it save to the intended recipient.

[epicfaace]

closing in favor of #2605