Skip to content

becomeDirty() Seems To Be Throwing Some Errors In Ember-2.x #102

@nadnoslen

Description

@nadnoslen
"Error: Assertion Failed: You modified "value" twice on <valet@component:-text-field::ember1671> in a single render. It was rendered in "component:-text-field" and modified in "component:-text-field". 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 new EmberError (http://localhost:3000/assets/vendor.js:35502:25)
    at Object.assert (http://localhost:3000/assets/vendor.js:35745:15)
    at Object.exports.assertNotRendered (http://localhost:3000/assets/vendor.js:45215:42)
    at propertyDidChange (http://localhost:3000/assets/vendor.js:45333:15)
    at set (http://localhost:3000/assets/vendor.js:47213:7)
    at Class._elementValueDidChange (http://localhost:3000/assets/vendor.js:68478:27)
    at Class.focusOut (http://localhost:3000/assets/vendor.js:68547:12)
    at Class.trigger (http://localhost:3000/assets/vendor.js:69542:23)
    at Class.superWrapper [as trigger] (http://localhost:3000/assets/vendor.js:67561:22)
    at Backburner.join (http://localhost:3000/assets/vendor.js:31479:31)"

I noticed this happening when we toggle a select boxes value for a model's relationship. Triggering the option choice from the select box also calls the model's becomeDirty() function. Once the model is saved, this error is presented in the console.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions