fix: do not call renderer for disconnected columns #7389
Merged
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.
Description
Added a check to
_updateItem()
method and a test to verify that removing thevaadin-grid-tree-column
doesn't throw.This fixes the following problem that was reported internally:
Did some debugging and here’s what happens in this case:
vaadin-grid-tree-column
and other columns are detached,disconnectedCallback()
is called. At this point,_grid
reference is cleareddataProvider
used by the first Grid is replaced withitems
array used by second Grid_dataProviderChanged
observer is called by thevaadin-grid
and it callsclearCache()
__updateVisibleRows()
which re-renders grid cells also for detached columns._updateItem
method where we don’t check ifcolumn._grid
is defined.Type of change