fix(zone.js): handle punctuation event names in node cleanup#68932
Open
SkyZeroZx wants to merge 1 commit into
Open
fix(zone.js): handle punctuation event names in node cleanup#68932SkyZeroZx wants to merge 1 commit into
SkyZeroZx wants to merge 1 commit into
Conversation
Widen the EventEmitter cleanup key matcher so event names are not limited to word characters before the trailing true/false marker. This keeps the existing removeAllListeners() cleanup flow while allowing string event names that contain punctuation or Unicode characters to be matched correctly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Widen the EventEmitter cleanup key matcher so event names are not limited to word characters before the trailing true/false marker.
This keeps the existing removeAllListeners() cleanup flow while allowing string event names that contain punctuation or Unicode characters to be matched correctly.
More context: https://issuetracker.google.com/u/1/issues/515882352