Editorial: tweak PropertyDefinitionEvaluation and ClassElementEvaluation #2470
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.
For the first commit: The
_enumerable_
parameter forPropertyDefinitionEvaluation
was always true; the parameter of the same name forClassElementEvaluation
was always false. Prior to #1668 PropertyDefinitionEvaluation was used for both object literals and classes. When it was split, the parameter became redundant.The second commit just fixes an oversight of mine from fe6b5ef (part of #2271).