You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many projects require dynamic changes to a column’s aggregation strategy at runtime.
Currently, I had to build a workarounds using states manually when I want a column to switch from one aggregation type to another (e.g., sum to count).
Providing a setAggregationFn method would create a straightforward pathway to swap aggregators on the fly, enhancing flexibility and reducing the need for custom hooks or ad-hoc state management.
I imagine it the methodlooking like this: column.setAggregationFn(key)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Many projects require dynamic changes to a column’s aggregation strategy at runtime.
Currently, I had to build a workarounds using states manually when I want a column to switch from one aggregation type to another (e.g., sum to count).
Providing a
setAggregationFn
method would create a straightforward pathway to swap aggregators on the fly, enhancing flexibility and reducing the need for custom hooks or ad-hoc state management.I imagine it the methodlooking like this:
column.setAggregationFn(key)
Beta Was this translation helpful? Give feedback.
All reactions