Sourced from react-i18next's changelog.
17.1.4
- fix(types): without
allowObjectInHTMLChildren, thechildrenof HTML elements now use React's own type (DOMAttributes<T>['children']) instead of theReactI18NextChildren | Iterable<ReactI18NextChildren>union. Both accept the same children, so nothing compiles differently. For default installs the globalHTMLAttributesaugmentation now repeats whatever@types/reactdeclares, so changes in React's types flow through instead of meeting a copy, and type errors on element children no longer list an extraIterable<...>. WithallowObjectInHTMLChildren: truenothing changes. First step of #1928.17.1.3
- fix(IcuTrans): numeric HTML entities above U+FFFF, like emoji, now decode to the right character.
"Hello 👋 <0>friend</0> &[#127881](https://github.com/i18next/react-i18next/issues/127881);"rendered U+F44B and U+F389, private-use glyphs that usually show as a box, instead of 👋 and 🎉: the decoder usedString.fromCharCode, which keeps only the low 16 bits of the code point. This shows up with translations that a TMS or CMS exports HTML-encoded. Entities above U+10FFFF, which are no valid code points, now stay as written instead of becoming U+0000. Entities below U+10000, including surrogate pairs written as two entities, decode as before. Thanks@​nk-batman21(#1940).17.1.2
- fix(Trans): when the only child is a string, a tag whose index the children don't have now renders its own text.
<Trans i18nKey="welcome">Welcome</Trans>with"Welcome <1>friend</1>"renderedWelcome e, anddefaults="Hi <1>there</1>"with the childHirenderedHi i. The fallback for a single object of components ({{ 1: <strong /> }}) looked the tag up on the string and rendered one of its characters. It now applies only when that child is an object, so{{ 1: <strong /> }}renders as before, and the tag falls back to its inner text, as it already did with several children or with a number or an element as the only child. This also stops a single-entry array child holdingnull({[null]}, e.g. from a.mapthat returnednull) from throwingCannot read properties of null. Thanks@​Cayan(#1939).17.1.1
- fix(Trans): with
componentsas an object with index keys, the component for key0is now rendered.components={{ 0: <a href={path} /> }}with"You're eligible. <0>Get started here.</0>"rendered the text without the link, a self-closing<0/>rendered nothing, and in<0>a <1>b</1></0>both elements were lost, while keys1and up and the array form worked. The object was passed on as the indexed children, so<0>resolved to the object itself. It is now looked up by key, like a named components map. This also fixes an arraycomponentsnext toreact.transDefaultProps.components, which the merge turns into such an object ({ Bold, 0, 1 }) and so lost its first entry, and a self-closing named tag in a mixed object ({ 0: <a />, Bold: <b /> }with<Bold/>), which rendered as the text<Bold />. Arrays, named maps and index objects starting at1render as before. Thanks@​nk-batman21(#1938).
290e8ab
17.1.4aeb94d1
changelog for 17.1.43fecad7
fix(types): use React's own children type unless
allowObjectInHTMLChildren is...696c0f5
17.1.3094943a
builda73495c
changelog for 17.1.39a36388
fix(IcuTrans): decode numeric entities above U+FFFF (#1940)53a810c
17.1.201aa762
build7867981
changelog for 17.1.2Sourced from react-resizable-panels's releases.
4.14.8
- Fix "Stacking order can only be calculated for elements with a common ancestor" error thrown by the document
pointermovehandler when the event target is removed from the DOM during dispatch. Detached targets are now treated as viable hit targets. - #771- Fix
GroupandGridsetLayout()andPanelresize(),collapse(), andexpand()validating against pixel-based constraints for the previous group size when called before the group'sResizeObserverran (e.g. from an application's ownResizeObserver). - #770
Sourced from react-resizable-panels's changelog.
4.14.8
- Fix "Stacking order can only be calculated for elements with a common ancestor" error thrown by the document
pointermovehandler when the event target is removed from the DOM during dispatch. Detached targets are now treated as viable hit targets. - #771- Fix
GroupandGridsetLayout()andPanelresize(),collapse(), andexpand()validating against pixel-based constraints for the previous group size when called before the group'sResizeObserverran (e.g. from an application's ownResizeObserver). - #770
c19f0a9
4.14.7 -> 4.14.8625ef2d
Validate imperative layout changes against the group's current size (#772)64c5be9
Fix "Stacking order can only be calculated for elements with a
common ancesto...