@sendbird/uikit-react
Advanced tools
Changelog
[v3.2.0] (Sep 27 2022)
Features:
Fixes:
o
penChannel casing in type defnDev. Env:
enzyme
and react-test-renderer
react
version to v18storybook
version to v6.5.10jest
and babel-jest
to v29jsdom
to v20jest-environment-jsdom
global-jsdom
testing-library
(@testing-library/react
and @testing-library/jest-dom
)testing-library
instead of the enzyme
and `react-test-rendererChangelog
[v3.1.3] (Sep 19 2022)
Features:
@sendbird/uikit-react/handlers/SessionHandler
import SessionHandler from '@sendbird/uikit-react/handlers/SessionHandler'
config.isREMUnitEnabled
-> true on SendbirdProvider
to use "rem" unitsFixes:
isReactionEnabled
to the <TextMessageItemBody />isReactionEnabled
to the <OGMessageItemBody />isReactionEnabled
to the <FileMessageItemBody />isReactionEnabled
to the <ThumbnailMessageItemBody />isReactionEnabled
to the <UnknownMessageItemBody />Changelog
[v3.1.2] (Aug 31 2022)
Fixes:
Type defn: Change type of react elements to React.ReactElement
React.ReactNode
and React.Component
to React.ReactElement
'ts' as const
ReactNode could be string | number | null | undefined | ReactElement | portal
and this(expecting string or number) causes warning when we use it like <CustomComp />
// in the component
{ renderMessage } = props
const CustomMessage = useMemo(() => {
return renderMessage({ ... });
}, []);
return (
<div>
<CustomMessage />
</div>
);
so expecting ReactElement is better for our case
Fix message grouping: Set isMessageGroupingEnabed to true(was set to false during v2 migration)