-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Table fully redrawing on column changed #381
Comments
Stuck on a similar issue, I'm updating a column, changing the status of a record. It automatically resets the table state, |
The entire table seems to be glitching (redrawing) on pagination, and sometimes on its own (still figuring out why) |
I rewrote this repo as an internal jsx file and it works. Had to remove the
|
Same issue here, i always normally recreate a grid component, but it's heavy... Each time you need to add dynamic options the grid redraw.... https://codesandbox.io/s/gridjs-react-server-side-forked-lsrcfv?file=/src/App.js And he is making an Api call too.... |
The issue of rerendering on state change still exists. Even on the docs page, you can see the screen flashes when clicking the add new record button: |
Descriprion of the bug
I have a sign with a "select row" checkbox. After I click on the checkbox id of this row (which is stored in the cell with index 2) is added to my side. Actually, everything works as it should, however, when the checkbox state changes from checked = {true} to checked = {false} or vice versa, the table is completely redrawn and throws us to the very beginning. That is, if we have scrolled a little and clicked on "select a row", then we will be sent to the top of the table and it will be completely redrawn. Also in the table there is a column with images and, accordingly, they are constantly being rerendered, which leads to unnecessary http requests and frequent animation of the image "loading". Most likely the problem is in the wrong keys for the components in the plugin. Please fix this bug.
Desktop :
The text was updated successfully, but these errors were encountered: