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
This is a stripped-down version of the issue I originally saw, but note that in my actual code, I use the intent field for validation as well, which is calculated at render time (as opposed to cached in state like the example), and changing the value using setStatedoes cause the intent to change in the DOM, but not the text content (as here).
In my use-case, the table is editable and part of a controlled component, so every time you change something it makes the callback -> props roundtrip, which means I hit this issue all of the time. :(
The text was updated successfully, but these errors were encountered:
Bug report
Steps to reproduce
TableEditableExample
component and select it such that it's assigned to$r
in the console$r.setState({ sparseCellData: Object.assign({}, $r.state.sparseCellData, { '1-1': 'foo' }) })
in the consoleActual behavior
Expected behavior
This is a stripped-down version of the issue I originally saw, but note that in my actual code, I use the
intent
field for validation as well, which is calculated at render time (as opposed to cached in state like the example), and changing the value usingsetState
does cause the intent to change in the DOM, but not the text content (as here).In my use-case, the table is editable and part of a controlled component, so every time you change something it makes the callback -> props roundtrip, which means I hit this issue all of the time. :(
The text was updated successfully, but these errors were encountered: