[data grid] disable processor cleanups in development / testing #16400
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.
Trying to fix a hairy issue discovered here:
#16395 (comment)
The problem is that
useFirstRender
doesn't work properly in StrictMode. It is only called once, but everything else is called twice, meaning that processors are improperly cleaned up. Trying to see if we can just disable cleanups in development to preserve the functionality ofuseFirstRender
with StrictMode.If
useFirstRender
doesn't work properly with StrictMode, and we cleanup processors incorrectly, we have a few problems:useEffect
, so ordering of hooks is extremely important inuseDatagridComponent
hook