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

Unable to traverse some ember data relationships in the Inspector #791

Closed
christophermlne opened this issue Apr 26, 2018 · 2 comments · Fixed by #847
Closed

Unable to traverse some ember data relationships in the Inspector #791

christophermlne opened this issue Apr 26, 2018 · 2 comments · Fixed by #847
Labels

Comments

@christophermlne
Copy link

christophermlne commented Apr 26, 2018

Looking at the screenshot of the ember inspector UI, I can click through the ancestors relationship, but not any of the others that are identified as <DS.PromiseObject:...> or <DS.PromiseManyArray:...>. Clicking on those relationships causes the warning included below to be printed to the console.

Screenshot:
image

Console warning that results from clicking on the DS.Promise relationships

This is likely a bug in the inspector itself.
You can report bugs at https://github.com/emberjs/ember-inspector.
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.**

Info

Ember Inspector | 3.0.0
Ember | 3.1.0
Ember Data | 3.1.1
jQuery | 3.3.1
Ember Simple Auth | 1.6.0
Ember Paper  | 1.0.0-beta.4
Model Fragments | 3.0.0


@RobbieTheWagner
Copy link
Member

Hi @christophermlne, thanks for letting us know about this. It looks like the issue is here

if (object._debugInfo && typeof object._debugInfo === 'function') {

Would you be interested in working on a fix?

@christophermlne
Copy link
Author

christophermlne commented Apr 27, 2018

@rwwagner90 I will have a look at it tonight after work and report back
This looks straightforward. I will submit a PR tonight or early next week.

RobbieTheWagner added a commit that referenced this issue Jul 29, 2018
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 added a commit that referenced this issue Jul 30, 2018
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.**
```
cyril-sf pushed a commit to cyril-sf/ember-inspector that referenced this issue 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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants