Event API: responder event types should not re-register on EventComponent update #15514
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.
This PR fixes a bug where static root events incorrectly get registered multiple times. We were incorrectly re-registering the responder events during the
updateEventComponent
phase, when really, this never needed to be the case. This is because theresponder
on an event component should be static and treated as an immutable object. I've added a DEV timeObject.freeze
to the responder to ensure this remains consistent.