Replies: 1 comment 1 reply
-
It is best to control the state and hoist it up to where you want to have access to it. If you don't want to create a useState for every individual state, you can create 1 state, setState instead. See the Fully Controlled Example You could also technically make a useEffect that listens to |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey, I might have missed in the docs/examples but I can't find a way to listen without controlling the table's internal state. The methods
onSortingChange
|onExpandedChange
|onPaginationChange
all implies having to manage the state/update, what if I just wanted to be notified when that happens, is it possible right now ?Beta Was this translation helpful? Give feedback.
All reactions