[v6] resolvedState right after state change stay the same with babel 7, but new after a little timeout #2017
Replies: 1 comment
-
Seems it's not a Babel case. It's a difference between 6.7 and 6.11 versions of react-table package. How can i trgger onFetchData in 6.11 by changing filtered props of react-table? |
Beta Was this translation helpful? Give feedback.
-
Hi everyone.
package: "react-table": "^6.7.4"
If i change filtered attr of table i get newResolvedState only after timeout (
), but not immediatly after table state changed. This seems lead to not firing onFetchData because of this
node_modules/react-table/src/lifecycle.js:44
newState seems the same as oldState.
But in babel 6 there's no such problems
My current configuration:
package.json
babel.config.json:
My previous working tables configs:
package.json:
.babelrc:
Any thoughts what causing such problems with react-tables?
Beta Was this translation helpful? Give feedback.
All reactions