v5.0.0 #1399
AlekseyManetov
announced in
Announcements
v5.0.0
#1399
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
5.0.0 - 06.06.2023
Themes
This release introduces Themes support.
@epam/uui
package now contains components, which can be styled differently according to an applied Theme - a set of global CSS variables.@epam/promo
and@epam/loveship
packages are re-built on top of@epam/uui
package. This allows us to unify codebase, and reduce differences between 'loveship' and 'promo'. We also aligned APIs, functionality and visual appearance between 'promo' and 'loveship' skins, as a result, we removed or deprecated some props or their values.Pay attention that this release requires some additional actions for the library to work properly.
You can find migration guide and full list of changes here.
Note: Currently, we use Themes internally to implement Loveship and Promo. In future, we allow UUI users to build their own themes, and using Themes variables for customization. However, in this release we haven’t yet finalized Themes APIs (CSS variables names). We can’t yet recommend using Themes internals, e.g. override Themes CSS variables for customization.
Testing facilities and documentation
@epam/uui-test-utils
package. It provides a set of helpers, utils and mocks which facilitate creation of unit tests for UUI components.Also, it contains a Cookbook describing typical use cases with code examples as well as frequent questions & answers.
DataSources documentation
Note that this is the first revision of this doc, so we would appreciate your feedback and have plans to continuously improve this documentation.
ESM modules support
Other changes
@epam/assets
package and "assets" folders inside promo and loveship packages were cleaned up: some "*.scss" files were deleted. Please copy any missing files directly to your project if they are still needed.initialFilter
prop, if you need to provide any initial state for hook, pre-generate an url link with this state on you side.IEditable
props, use them for cases when you need to store DataTableState by yourself. If passed it assumed that you will handle all state changes on your side and hook will not store any state into url.enableLegacyContext
prop was deleted./auth/login
for the apps, which doesn't handle this themselves.If an app doesn't handle
/auth/login correctly
, this needs to be implemented implicitly. There are several options:<script>window.opener && window.opener.postMessage("authSuccess", "*")</script>
window.opener && window.location.pathname === '/auth/login' && window.opener.postMessage("authSuccess", "*");
window.opener && window.opener.postMessage("authSuccess", "*")
shrink
property was removed, as it was announced in 4.9.0 version.renderBody
prop.isAlwaysVisible
presets
prop to rangeDatePicker filterfilter
prop for datePicker and rangeDatePicker filtersimplicit
cascade selection mode. In this mode selecting a parent node means that all children are considered checked,but only the checked parent is present in the Picker's value or DataSourceState.checked array.
onOpenChange
propNotificationCard
component instead ofSnackbarCard
for notification type errorsonNotificationError
to render notifications with custom markup and configured the notification duration.inputCx
andbodyCx
props for composed components like PickerInput and DatePickersWhat's Fixed
This discussion was created from the release v5.0.0.
Beta Was this translation helpful? Give feedback.
All reactions