@opengeoweb/theme 2.1.0 → 2.1.4

package/README.md

@@ -97,7 +97,7 @@ export const Wrapper: React.FC = () => (
 2.  Use the style/color in your component. The theme palette can be found as `geowebColor` property inside the `theme.palette` of the MUI Theme
 
 ```javascript
-const useStyles = makeStyles((theme) => ({
+const useStyles = makeStyles((theme: Theme) => ({
   button: {
     border: theme.palette.geowebColors.buttons.flatMouseOver.border,
     '&:hover': {
@@ -144,7 +144,7 @@ const TimeSliderLegend: React.FC<TimeSliderLegendProps> = (
 
 ```javascript
 // libs/core/src/lib/components/TimeSlider/TimeSliderLegend/TimeSliderLegendRenderFunctions.tsx
-import { Theme } from  '@material-ui/core';
+import { Theme } from  '@mui/material';
 
 export const renderTimeSliderLegend = (
   context: CanvasRenderingContext2D,
@@ -321,7 +321,7 @@ Contains demo stories with MUI components. Every story is build with the `StoryW
 - The **Elevation** shows all elevations we currently have. These can be used for defining `box-shadow` for elements. If you want to use the elevation in code:
 
 ```javascript
-const useStyles = makeStyles((theme) => ({
+const useStyles = makeStyles((theme: Theme) => ({
   header: {
     boxShadow: theme.shadows[1], // elevation_01
   },
@@ -454,7 +454,6 @@ This footer is only used for when the wrapper is resizable. Therefore it would m
 
 ## Known issues
 
-- **React.Strictmode** does not work well with dynamic changing of themes. For now we have disabled it, but it should be activated again after the update to MUI 5. https://gitlab.com/opengeoweb/opengeoweb/-/issues/965
 - **Expect unit tests to fail** when using components with the theme. This is easily fixed by wrapping your test with the `ThemeProvider` from the `theme` lib. Don't import the ThemeProvider wrapper in the failed test, but use the `CoreThemeProvider` or `CoreThemeStoreProvider` found in [`libs/core/src/lib/components/Providers/Providers.tsx`](https://gitlab.com/opengeoweb/opengeoweb/-/blob/master/libs/core/src/lib/components/Providers/Providers.tsx#L36)
 - There are some **storybook bugs** with stories with Themes. When switching stories with new and old theme, it could be possible that some colors are rendered wrong. This is probably happening because one of the stories with old theme has `React.Strictmode` activated. This is only happening in storybook, and when refreshing page the colors should be correct. This will fix itself when we have `gwTheme` removed.
 - **MUI 5** makes it easy to add custom variants to components, so we should wait for that release before investing more heavy in theme stories: https://next.material-ui.com/customization/theme-components/#adding-new-component-variants . Check the progress of the release of [v5 here](https://github.com/mui-org/material-ui/milestone/44)
@@ -472,10 +471,6 @@ Other libs where `ThemeProvider` from `theme` should be used and `gwTheme` shoul
 - [ ] form-fields (**TICKET TO BE CREATED**)
 - [ ] shared (**TICKET TO BE CREATED**)
 
-Another point of the roadmap is upgrade to MUI5. This is complete when all `@material-ui` references have been removed from the code
-
-- [ ] Investigate impact of upgrade to MUI5 https://gitlab.com/opengeoweb/opengeoweb/-/issues/1355
-
 ## Unit testing
 
 ```