fix: Make sure that tagToJSPropNamesMapping is initialized before being used #7941
Conversation
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
MatiPl01
commented
Jul 30, 2025
tjzel
approved these changes
Jul 30, 2025
MatiPl01
deleted the
@matipl01/faster-tagToJSPropNamesMapping-initialization
branch
MatiPl01
added a commit
that referenced
this pull request
Jul 31, 2025
…ng used (#7941) ## Summary This PR should fix the issue when the `global._tagToJSPropNamesMapping` was accessed before being created.
This was referenced Jul 31, 2025
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR should fix the issue when the
global._tagToJSPropNamesMappingwas accessed before being created.