Skip to content
This repository was archived by the owner on Apr 4, 2019. It is now read-only.

Conversation

Saranya-Raaj
Copy link
Contributor

@stefanpenner
Copy link
Contributor

this needs tests

@Saranya-Raaj
Copy link
Contributor Author

I am facing issues in running test cases. I'll commit once i am able to run.

@Saranya-Raaj
Copy link
Contributor Author

@stefanpenner I have added a test case.

@rwjblue
Copy link
Contributor

rwjblue commented Feb 5, 2016

Can you squash?

@Saranya-Raaj Saranya-Raaj force-pushed the eachhelper-destroyelement branch from 17893f1 to 3ea0c7d Compare February 5, 2016 14:44
@Saranya-Raaj
Copy link
Contributor Author

@rwjblue done

visitChildren(morph.childNodes, function (node) {
clearMorph(node, env, true);
});
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can someone explain the logic of this change? I don't see how clearing all the morphs when adding a new item is the right thing to do.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

willDestroyElement not firing in {{each}} else

4 participants