fix(components): guard event.persist() calls #14482
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.
Raised in slack
Even though
persist()
is available and just a noop in later versions of react that don't have event pooling anymore, we still need to guard calls to these. It was pointed out that if we begin to callpersist()
, it can break tests where event handlers are mocked. Example:Changelog
Changed
event.persist()
calls to be guarded viaevent?.persist?.();
References