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.
Tracked properties sometimes throw error when updated
See original GitHub issueThanks for your work!
js-data.js:6623 Uncaught (in promise) TypeError: Cannot read property ‘indexOf’ of undefined
version: 3.0.0-rc.5
changed:undefined
changing:true
current:"http://localhost:8000/media/images/blabla/8679ae5a-4f7.jpg"
index:undefined
previous: undefined
this: undefined
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Tracked Properties Updates - Ember RFCs
Observers and computed properties will throw an error if they attempt to watch a getter which is not marked as dependentKeyCompat. Debugging ...
Read more >Update method throws an exception, because the entity is ...
Problem: I have an entity "Product" which contains the following update method which is used to update the properties of the entity with...
Read more >Tracked Properties - size limit - MSDN - Microsoft
I've been using tracked properties for a while now, seem to have hit a size issue. I'm tracking the payload received in messages...
Read more >Tracked properties are non-enumerable · Issue #18220 - GitHub
This seems bad and confusing so I suspect it is unintentional. The text was updated successfully, but these errors were encountered: ...
Read more >Power Automate - Run Time Part 2: Tracked Properties and ...
We will then look into handling and capturing error information within actions to help troubleshoot and report on failing actions or flows.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m having this issue too. Seems like it happens when there are properties in a newly created model which are
undefined(having no default value and don’t have been set between creation and saving) and then new values come from the server.When you make sure you have default values for every property you don’t set after creation, everything works.
I think this is a bug. js-data should allow to have empty properties when saving a new model.
@BennyAlex Could you create a plunker or stackblitz or jsfiddle or something with code that reproduces the error?