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

2.14.6 - Error loading relationships in templates You modified "X" twice #5082

Closed
urbany opened this issue Jul 21, 2017 · 2 comments
Closed

Comments

@urbany
Copy link

urbany commented Jul 21, 2017

Hi, i just upgraded from: 2.13.2 to 2.14.6.

And now some templates where I was successfully doing:

{{ car.category }}

Where car is a model which has a category defined like: category: belongsTo()

Throws an error:

Assertion Failed: You modified "category" twice on <my-project@model:car::ember1007:1011> in a single render. It was rendered in "component:table-row" and modified in "component:table-row". This was unreliable and slow in Ember 1.x and is no longer supported. See https://github.com/emberjs/ember.js/issues/13948 for more details.
at Object.assert (/assets/vendor.js:29556:15)
    at Object.exports.assertNotRendered (/assets/vendor.js:39055:42)
    at propertyDidChange (/assets/vendor.js:39172:15)
    at Class.propertyDidChange (/assets/vendor.js:55148:41)
    at Class.notifyPropertyChange (/assets/vendor.js:55163:12)
    at InternalModel.notifyPropertyChange (/assets/vendor.js:216173:20)
    at BelongsToRelationship.updateLink (/assets/vendor.js:213058:24)
    at BelongsToRelationship.push (/assets/vendor.js:213137:14)
    at Relationships.get (/assets/vendor.js:214144:22)
    at Class.get (/assets/vendor.js:221824:49)

If i add {{debugger}} before that line in the template and try in the console get('car.category') I get the same error, but the second time it works correctly, can this be something to the new lazily load of relationships?

@kumkanillam
Copy link

I am not sure, but this may be related to #4942

@urbany
Copy link
Author

urbany commented Jul 22, 2017

@kumkanillam thank you very much!
It's the same bug, so I'm gonna close this and follow that issue.

@urbany urbany closed this as completed Jul 22, 2017
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

No branches or pull requests

2 participants