Skip to content

fix(modifyRows): modifyRows uses the new entity when using enableRowHashing #5917

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

Merged
merged 3 commits into from
Dec 29, 2016
Merged

fix(modifyRows): modifyRows uses the new entity when using enableRowHashing #5917

merged 3 commits into from
Dec 29, 2016

Conversation

mportuga
Copy link
Member

@mportuga mportuga commented Dec 28, 2016

When using enableRowHashing (which is set right now to true as default), modifyRows match the old and the new row but not using the new entity at all.

Credit to @idangozlan for the fix. This PR merely adds unit tests to his work.


expect(grid.rows.length).toBe(1);
function testInitialChange() {
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it necessary to run this in every test? Shouldn't this just but one 'it'?

Copy link
Member Author

Choose a reason for hiding this comment

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

good point. I will make that change.

@mportuga
Copy link
Member Author

@jeremytowne I made the change you suggested

@mportuga mportuga merged commit 138d149 into angular-ui:master Dec 29, 2016
@mportuga mportuga deleted the issues/fixModifyRows branch December 29, 2016 19:30
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

Successfully merging this pull request may close these issues.

4 participants