2.10.2-with-improved-backtracking-assertion#10
Open
GavinJoyce wants to merge 2 commits intomasterfrom
Open
Conversation
This was referenced Dec 20, 2016
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
example 1 a
"Assertion Failed: You modified "model.name" twice on [object Object] in a single render. It was rendered in "backtracking/templates/example1.hbs" and modified in "component:component-that-changes-name-on-init". 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."example 1 b
"Assertion Failed: You modified "person.name" twice on [object Object] in a single render. It was rendered in "component:component-that-wraps-the-component-that-changes-name-on-init" and modified in "component:component-that-changes-name-on-init". 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."example 2
"Assertion Failed: You modified "otherName" twice on <backtracking@component:component-with-set-in-get::ember375> in a single render. It was rendered in "component:component-with-set-in-get" and modified in "component:component-with-set-in-get". 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."example 3
"Assertion Failed: You modified "latestCount" twice on <backtracking@controller:example3::ember365> in a single render. It was rendered in "backtracking/templates/example3.hbs" and modified in "component:component-which-emits-an-action-on-init". 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."example 4
"Assertion Failed: You modified "otherName" twice on <backtracking@component:component-with-set-in-get::ember399> in a single render. It was rendered in "component:component-with-set-in-get" and modified in "component:component-with-set-in-get". 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."example 5 a
"Assertion Failed: You modified "model.name" twice on [object Object] in a single render. It was rendered in "controller:example1 (with the render helper)" and modified in "component:component-that-changes-name-on-init". 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."example 5b
"Assertion Failed: You modified "person.name" twice on [object Object] in a single render. It was rendered in "controller:example1 (with the render helper)" and modified in "component:component-that-changes-name-on-init". 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."