Errors with Ember v3.22
See original GitHub issueJust tried upgrading an app to Ember v3.22 and started getting some errors in changeset.
index.js:172 Uncaught (in promise) Error: Assertion Failed: You attempted to update `_changes` on `changeset:[object Object]`, but it had already been used previously in the same computation. Attempting to update a value after using it in a computation can cause logical errors, infinite revalidation bugs, and performance issues, and is not supported.
`_changes` was first used:
The same happens with _errors as well.

Version
changeset v 3.8.2 (also tested with latest version but same occurs. ) ember v 3.22
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Errors - 4.7 - Ember API Documentation
Every Model has an errors property that is an instance of Errors . This can be used to display validation error messages returned...
Read more >Facing issue after update ember from 3.0.0 to 3.22.0
After updating ember from 3.0.0 to 3.22.0 using ember-cli-update and install npm packges. And finally hit ember s it throws the bellow error...
Read more >Dealing with errors in Ember with Custom API Responses
I started working with Ember recently and one of the things I've had to deal with is dealing with custom API responses.
Read more >ember-error-for
Simple wrapper for javascript constraint error messages. It should satisfy very simple forms. Demo. Compatibility. Ember.js v3.16 or above ...
Read more >Conflicting Type Dependencies - ember-cli-typescript
bin/tsc --noEmit node_modules/@types/ember__object/index.d.ts:23:22 - error TS2300: Duplicate identifier 'EmberObject'. 23 export default class EmberObject ...
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

@sinankeskin 👋 This is similar to this case. You might have to adjust when/how the changes is created then updated. The problem is something was read-then-written in the same computation in the same “tick”.
https://github.com/poteto/ember-changeset/issues/602
I’ve fixed this with a creating middle classes. Works perfect now. Thanks a lot @snewcomer Appreciated.