Patch fixes #6755
Patch fixes #6755
Conversation
|
## API Changes
unknown top level export { type: 'any' } @react-aria/collectionscreateLeafComponent createLeafComponent<E extends Element, P extends {}> {
type: string
- render: (P, ForwardedRef<E>, any) => ReactNode
+ render: (P, ForwardedRef<E>, any) => ReactElement
returnVal: undefined
}createBranchComponent createBranchComponent<E extends Element, P extends {
children?: any
}, T extends {}> {
type: string
- render: (P, ForwardedRef<E>, Node<T>) => ReactNode
+ render: (P, ForwardedRef<E>, Node<T>) => ReactElement
useChildren: (P) => ReactNode
returnVal: undefined
}createHideableComponent createHideableComponent<P = {
}, T> {
- fn: (P, React.Ref<T>) => ReactNode | null
+ fn: (P, React.Ref<T>) => ReactElement | null
returnVal: undefined
}@react-aria/utilsscrollIntoView-
+getSyntheticLinkProps {
+ props: LinkDOMProps
+ returnVal: undefined
+} |
getSyntheticLinkPropsalongside the newuseSyntheticLinkProps. This way if someone pins to an older version of an upstream package like@react-aria/table, but the caret dependency on@react-aria/utilsresolves to a newer version, the packages are still compatible.ReactElementas the return type of components rather thanReactNode. Support for returning types other than JSX elements existed in React since 16 but not in the types until 18. TypeScript will complain that a component can't be rendered as a JSX element at the usage site if a function component returns anything other than an element with old react versions. See @types/react Make it possible to render a string from a functional component DefinitelyTyped/DefinitelyTyped#20544.TabListStateContextinTabPanelso that nested tabs work and don't connect to the wrong state object. Added test and story.@react-stately/virtualizerfrom@react-types/sidenav. Not sure why it was even there and that package is unused, but it caused multiple versions to be installed in our mono repo.