@opengeoweb/theme 2.1.3 → 2.1.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -6
- package/{theme.esm.js → index.esm.js} +400 -268
- package/{theme.umd.js → index.umd.js} +405 -273
- package/lib/components/Theme/ThemeContext.d.ts +1 -1
- package/lib/components/Theme/darkTheme.d.ts +1 -1
- package/lib/components/Theme/gwTheme.d.ts +1 -7
- package/lib/components/Theme/lightTheme.d.ts +1 -1
- package/lib/components/Theme/types.d.ts +1 -1
- package/lib/components/Theme/utils.d.ts +3 -3
- package/lib/stories/Backdrop.stories.d.ts +1 -0
- package/package.json +7 -7
package/README.md
CHANGED
|
@@ -144,7 +144,7 @@ const TimeSliderLegend: React.FC<TimeSliderLegendProps> = (
|
|
|
144
144
|
|
|
145
145
|
```javascript
|
|
146
146
|
// libs/core/src/lib/components/TimeSlider/TimeSliderLegend/TimeSliderLegendRenderFunctions.tsx
|
|
147
|
-
import { Theme } from '@material
|
|
147
|
+
import { Theme } from '@mui/material';
|
|
148
148
|
|
|
149
149
|
export const renderTimeSliderLegend = (
|
|
150
150
|
context: CanvasRenderingContext2D,
|
|
@@ -454,7 +454,6 @@ This footer is only used for when the wrapper is resizable. Therefore it would m
|
|
|
454
454
|
|
|
455
455
|
## Known issues
|
|
456
456
|
|
|
457
|
-
- **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
|
|
458
457
|
- **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)
|
|
459
458
|
- 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.
|
|
460
459
|
- **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
|
|
|
472
471
|
- [ ] form-fields (**TICKET TO BE CREATED**)
|
|
473
472
|
- [ ] shared (**TICKET TO BE CREATED**)
|
|
474
473
|
|
|
475
|
-
Another point of the roadmap is upgrade to MUI5. This is complete when all `@material-ui` references have been removed from the code
|
|
476
|
-
|
|
477
|
-
- [ ] Investigate impact of upgrade to MUI5 https://gitlab.com/opengeoweb/opengeoweb/-/issues/1355
|
|
478
|
-
|
|
479
474
|
## Unit testing
|
|
480
475
|
|
|
481
476
|
```
|