Allows access to methods when class instance used for x-data #4038
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.
Currently, if a class instance is used as the data scope, instance methods (and inherited properties shudders) are not accessible in expressions.
This is due to only checking for own properties in
mergeProxies
.This changes this to use
Reflect.has
to better reflect the actual operation being performed, and uses that same behavior in other places doing this check for consistency. (Of note, I found in some testing that usingReflect.ownKeys
in theownKeys
trap caused some very strange call stack issues).(Note on using Class instances in general: actually private instance properties/methods will not be accessible from other methods on that class instance due to how the proxy reflection actually works).