[BUGFIX beta] Ensure accessing a "proxy" itself does not error. #16274
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.
Prior to this change, if
Ember.get
(orthis.get
) is used to access a property that is an Ember.Object with anunknownProperty
that always returns a non-undefined
value, the internals ofEmber.get
would check if that property is a "descriptor" and (due to theunknownProperty
never returningundefined
) the dev time assertion for accessing a proxy's content without usingEmber.get
would be triggered.Fixes #16263