[core] Call useGridColumnPinning
before useGridColumns
#3676
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.
Each hook using
GridPreProcessingGroup.hydrateColumns
and called afteruseGridColumns
causes a full additional pre-processing on mount because the columns need to be pre-processed before and after the 1st call of the feature hook.Whereas if the feature hook is before, the pre-processing will only run once when
useGridColumns
is called.The same applies to other pre-processings but this one is especially heavy when we have a lot of columns and has a lot of hooks hooked to it, so we could quickly run 5 or more useless pre-processings if we don't take care.
To more we move toward event listeners and pre-processors, the more
useGridRows
anduseGridColumns
should be late in the feature hook call order.Same things as described here #3387 (comment)