Merge pull request #1176 from rvsia/updateDocMUI5

Update docs for MUI5 mapper

Author: Hyperkid123

packages/react-renderer-demo/src/pages/provided-mappers/mui-component-mapper.md

@@ -1,12 +1,19 @@
 import DocPage from '@docs/doc-page';
 import ComponentMapperBar from '@docs/component-mapper-bar';
+import Alert from '@mui/material/Alert';
 
 <DocPage>
 
 # MaterialUI mapper
 
 <ComponentMapperBar prefix="mui" href="https://mui.com/" />
 
+<br />
+
+<Alert severity="warning">MUI component mapper is using MUI5. Check the migration guide below.</Alert>
+
+<br />
+
 MaterialUI mapper provides components from [MaterialUI React library](https://mui.com/).
 
 ## Installation
@@ -38,17 +45,17 @@ This field will show the error immediately.
 
 ## Migration to version 5
 
-MaterialUI (now known just as MUI) recently released a version 5 that introduces a lot of new features and some breaking changes. Data Driven Forms follows this release with our integration in `mui-component-mapper`. Due to inability to release new version of packages independently, we are going to introduce new changes as a feature release to not disrupt any other mappers. We deeply apologise for any issues it can introduce, but we agreed that this is the best way that won't break any of our current workflows.
+MaterialUI (known just as MUI now) released a version 5 that introduces a lot of new features and some breaking changes. Data Driven Forms follows this release with our integration in `mui-component-mapper`. Due to inability to release new version of packages independently, we are going to introduce new changes as a feature release to not disrupt any other mappers. We deeply apologise for any issues it can introduce, but we agreed that this is the best way that won't break any of our current workflows.
 
 ### Migration
 
 #### Convert your app to use MUI 5
 
 Please follow [official migration guide](https://mui.com/guides/migration-v4/). *Note: emotion packages are being installed by the mapper itself.*
 
-#### Use beta version of the mapper
+#### Use new version of the mapper
 
-Use `3.16.0-v5-beta` version (or check if there is any newer version of v5 version [here](https://www.npmjs.com/package/@data-driven-forms/mui-component-mapper).)
+Use `3.16.0` and higher versions ([check here](https://www.npmjs.com/package/@data-driven-forms/mui-component-mapper).)
 
 <br />
 
@@ -71,11 +78,11 @@ Please lock your `mui-component-mapper` version in `package.json`:
 ```diff
 # package.json
 
-+ "@data-driven-forms/mui-component-mapper": "^3.15.5",
-- "@data-driven-forms/mui-component-mapper": "3.15.5",
+- "@data-driven-forms/mui-component-mapper": "^3.15.7",
++ "@data-driven-forms/mui-component-mapper": "3.15.7",
 ```
 
-For any future bug fixes, we will use `3.15` as a base version. (example: next bugfix would be `3.15.6` and these versions will be tagged as `deprecated`.)
+For any future bug fixes, we will use `3.15.7` as a base version. (example: next bugfix would be `3.15.8` and these versions will be tagged as `deprecated` in the npm registry.)
 
 In the near future, we will support bugfixes for Material-UI v4 mapper version, but no new features will be implemented. We are open to accept PRs by community. Also, this older version should work with the latest `react-form-renderer` at least until Data Driven Forms version 4 is released.