Fixed an issue with throwing an exception when HotTable
component state is changed
#10427
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
It seems that
render
done byFormulas
plugin while component state is changed causes an error. When we have an application which shows two orHotTable
each of them resets some internal properties (done by methods attached toref
attributes - see below).handsontable/wrappers/react/src/hotTable.tsx
Line 523 in b4d9477
handsontable/wrappers/react/src/hotTable.tsx
Line 526 in b4d9477
Any extra call of Hansontable's
render
method cause access tonull
ed values. Thus, an exception in thrown. This PR stops renderers actions from execution while component isn't mounted.How has this been tested?
Wrote application which use two instances of
HotTable
componentTypes of changes
Related issue(s):
Affected project(s):
handsontable
@handsontable/angular
@handsontable/react
@handsontable/vue
@handsontable/vue3
Checklist: