question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Clicking any Ember Data model throws error

See original GitHub issue

Describe the bug When trying to inspect the Ember Data store through Ember Inspector, I click the data tab, see a list of models present. If I then click any of the models in the list, an error is thrown by Ember Inspector, and the model is not loaded in the right panel.

To Reproduce Steps to reproduce the behavior:

  1. Open any Ember app with data in the store
  2. Click on the Data tab
  3. Select a model in the list view
  4. See error

Stack trace

This is likely a bug in the inspector itself.
You can report bugs at https://github.com/emberjs/ember-inspector.
Error message: ["__LEGACY_OWNER","__ARGS__","__HAS_BLOCK__","__PROPERTY_DID_CHANGE__"].any is not a function
Stack trace: TypeError: ["__LEGACY_OWNER","__ARGS__","__HAS_BLOCK__","__PROPERTY_DID_CHANGE__"].any is not a function
    at isInternalProperty (<anonymous>:4708:101)
    at addProperties (<anonymous>:4619:11)
    at ownProperties (<anonymous>:4596:12)
    at n.mixinDetailsForObject (<anonymous>:4384:21)
    at n.mixinsForObject (<anonymous>:4430:31)
    at n.sendObject (<anonymous>:4260:26)
    at n.inspectModel (<anonymous>:791:30)
    at b (https://getflights.com/assets/vendor-475803ed4a10495a95beaf31401ccdf4.js:1835:40)
    at n.trigger (https://getflights.com/assets/vendor-475803ed4a10495a95beaf31401ccdf4.js:2624:266)
    at <anonymous>:5079:16

Environment Ember version: 3.24.4 Ember data: 3.24.2 Ember Inspector: 4.5.3

Additional context

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:10 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
rwwagner90commented, Nov 22, 2021

@Windvis that is on purpose. ember_debug is what runs in the context of your Ember app. All the inspector app code itself we control and it shouldn’t have these issues.

1reaction
rwwagner90commented, Nov 22, 2021

Ah, thanks @Windvis, you are correct! Yes, converting to .some should work. Would you be interested in opening a PR?

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to throw Ember.js errors? - Stack Overflow
If you want to throw errors, use throw new Error("Message"); . The user gets redirected to error route. With Promises you can react...
Read more >
_updatePromiseProxyFor throws "used previously in the same ...
When an API payload is received with an association not already set on the Ember model, the following error is seen:.
Read more >
Router flow from link-to - Ember Guides
Router flow from link-to In this guide we will explore the steps Ember performs when a user clicks on a link generated by...
Read more >
The 8 Most Common Mistakes That Ember.js Developers Make
Common Mistake No. 1: Expecting the Model Hook to Fire When All Context Objects Are Passed In. Let's assume we have the following...
Read more >
Making error states easy to test | Mirage tips and tricks
In this video I want to show you how to test your application when it gets into an error state as a result...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found