@rebasepro/ui 0.12.1-canary.g389e9b2 → 0.12.1-canary.g4e7bcbf

package/dist/components/VirtualTable/VirtualTable.d.ts

@@ -1,11 +1,17 @@
 import React from "react";
 import { VirtualTableProps } from "./VirtualTableProps";
 /**
- * This is a Table component that allows displaying arbitrary data, not
- * necessarily related to entities or properties. It is the component
- * that powers the entity collections but has a generic API, so it
- * can be reused.
+ * `React.memo` is not generic-preserving: it takes the props type as its own
+ * type argument, so annotating the call with
+ * `VirtualTableProps<Record<string, unknown>>` pinned `T` at the boundary and
+ * discarded the `<T>` the inner function declares. The exported component was
+ * therefore not generic at all — every consumer got `Record<string, unknown>`,
+ * `columns` and `cellRenderer` were unrelated to `data`, and a caller writing
+ * `<VirtualTable<Post> …>` was told the component expects no type arguments.
  *
- * @group Components
+ * Re-asserting the call signature is the standard way to carry a type parameter
+ * across `memo`; it is the only cast here, and it restores the generic the
+ * implementation always had. Runtime behaviour is unchanged — this is the same
+ * memoized component under a type that describes it.
  */
-export declare const VirtualTable: React.NamedExoticComponent<VirtualTableProps<Record<string, unknown>>>;
+export declare const VirtualTable: <T extends Record<string, unknown>>(props: VirtualTableProps<T>) => React.ReactElement | null;

package/dist/index.es.js

@@ -5987,12 +5987,18 @@ var innerElementType = forwardRef(({ children, ...rest }, ref) => {
 	} });
 });
 /**
-* This is a Table component that allows displaying arbitrary data, not
-* necessarily related to entities or properties. It is the component
-* that powers the entity collections but has a generic API, so it
-* can be reused.
+* `React.memo` is not generic-preserving: it takes the props type as its own
+* type argument, so annotating the call with
+* `VirtualTableProps<Record<string, unknown>>` pinned `T` at the boundary and
+* discarded the `<T>` the inner function declares. The exported component was
+* therefore not generic at all — every consumer got `Record<string, unknown>`,
+* `columns` and `cellRenderer` were unrelated to `data`, and a caller writing
+* `<VirtualTable<Post> …>` was told the component expects no type arguments.
 *
-* @group Components
+* Re-asserting the call signature is the standard way to carry a type parameter
+* across `memo`; it is the only cast here, and it restores the generic the
+* implementation always had. Runtime behaviour is unchanged — this is the same
+* memoized component under a type that describes it.
 */
 var VirtualTable = React.memo(function VirtualTable({ data, onResetPagination, onEndReached, endOffset = 600, rowHeight = 54, headerHeight = 48, columns: columnsProp, onRowClick, onColumnResize, onColumnResizeEnd, filter: filterInput, checkFilterCombination, onFilterUpdate, sortBy, error, emptyComponent, onSortByUpdate, onScroll: onScrollProp, loading, cellRenderer, hoverRow, createFilterField, rowClassName, style, className, endAdornment, AddColumnComponent, initialScroll = 0, onColumnsOrderChange, extraData }) {
 	const sortByProperty = sortBy ? sortBy[0] : void 0;