Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Ember.get to get _debugInfo #847

Merged
merged 1 commit into from
Jul 30, 2018
Merged

Use Ember.get to get _debugInfo #847

merged 1 commit into from
Jul 30, 2018

Conversation

RobbieTheWagner
Copy link
Member

Resolves #791

I believe using Ember.get should fix this issue right @rwjblue?

It was this error:

Error message: Assertion Failed: You attempted to access the `_debugInfo` property (of <DS.PromiseObject:ember2256>).
Since Ember 3.1, this is usually fine as you no longer need to use `.get()`
to access computed properties. **However, in this case, the object in question
is a special kind of Ember object (a proxy). Therefore, it is still necessary
to use `.get('_debugInfo')` in this case.**

Resolves #791

I believe using Ember.get should fix this issue right @rwjblue?

It was this error:

```
Error message: Assertion Failed: You attempted to access the `_debugInfo` property (of <DS.PromiseObject:ember2256>).
Since Ember 3.1, this is usually fine as you no longer need to use `.get()`
to access computed properties. **However, in this case, the object in question
is a special kind of Ember object (a proxy). Therefore, it is still necessary
to use `.get('_debugInfo')` in this case.**
```
@RobbieTheWagner RobbieTheWagner merged commit 309d52c into master Jul 30, 2018
@RobbieTheWagner RobbieTheWagner deleted the get-for-proxy branch July 30, 2018 13:01
cyril-sf pushed a commit to cyril-sf/ember-inspector that referenced this pull request Mar 30, 2022
Resolves emberjs#791

I believe using Ember.get should fix this issue right @rwjblue?

It was this error:

```
Error message: Assertion Failed: You attempted to access the `_debugInfo` property (of <DS.PromiseObject:ember2256>).
Since Ember 3.1, this is usually fine as you no longer need to use `.get()`
to access computed properties. **However, in this case, the object in question
is a special kind of Ember object (a proxy). Therefore, it is still necessary
to use `.get('_debugInfo')` in this case.**
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to traverse some ember data relationships in the Inspector
2 participants