fix #2589: avoid invoking getter as side-effect #2592
Merged
Conversation
This file contains 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
of creating restorerer function. Check for the odd case where we actually force setting a value through accessor functions and only look up the value at that time. The alternative would be more elaborate, check if the descriptor had a `get` or a `value` field, and then decide, but this should do the trick.
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.
Purpose (TL;DR) - mandatory
Fix the issue in #2589 by checking for the odd case where we actually force setting a value through accessor functions and only look up the value at that time.
The alternative would be more elaborate, check if the descriptor had a
getor avaluefield, and then decide, but this should do the trick.How to verify - mandatory
npm installnpm testChecklist for author
npm run lintpasses