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
I had this problem in earlier versions (0.3), and when changing col meta with new columns and new custom controls etc I was nuking griddle with an unmount and then re-rendering from scratch rather than just triggering a re-render with the new col meta property as it should be.
This was gone in 0.6 and I was really happy about that, albeit if also resetting data dynamically I had to introduce a little delay between setting col meta and passing the new data into griddle to make it work (otherwise the behaviour was the same, new columns not being rendered).
Now after upgrading to 0.7 no matter what I do, delay or not, I cannot get griddle to see the new col meta. Probably gonna have to go back to nuking it since 0.7 solves other problems but it pains me greatly 😂
Any known workarounds to this?
The text was updated successfully, but these errors were encountered:
Hey - this is a real killer for us, we change columns dynamically and in 0.6 got to immediately see the change, now Griddle doesn't propagate the change at all
I had this problem in earlier versions (0.3), and when changing col meta with new columns and new custom controls etc I was nuking griddle with an unmount and then re-rendering from scratch rather than just triggering a re-render with the new col meta property as it should be.
This was gone in 0.6 and I was really happy about that, albeit if also resetting data dynamically I had to introduce a little delay between setting col meta and passing the new data into griddle to make it work (otherwise the behaviour was the same, new columns not being rendered).
Now after upgrading to 0.7 no matter what I do, delay or not, I cannot get griddle to see the new col meta. Probably gonna have to go back to nuking it since 0.7 solves other problems but it pains me greatly 😂
Any known workarounds to this?
The text was updated successfully, but these errors were encountered: