Feature Events Not Fired in Controller & Paging Not Initializing about igniteui-angularjs HOT 5 CLOSED

@mpavlinov check out commit 95f7774 where I updated igniteui-angular.js. I believe I fixed the bug that was stopping the directive from creating event subscriptions with the correct name.

I went through each of the samples and it seems to be okay, but I want you guys to give it a look before we merge it in.

from igniteui-angularjs.

I was aware of the grid feature events "problem". It was not actually a problem, but a specific case, because they are implemented as a nested jQuery UI widgets, thus before your fix in order to attach to the correct event you need to type the feature name as part of the event attribute name like this: event-paging-page-index-changed. Your fix seems to resolve this issue. I made a small code refactoring in order to make sure that this is related only to the grid features.

For the paging problem I had to do another fix, because changing of the grid data source should trigger re-binding of the grid.

You can merge these changes back to the master branch.

from igniteui-angularjs.

Makes sense regarding the event names. Will the change I am suggesting here create any potential for event names to collide?

from igniteui-angularjs.

I don't see any problem with your changes.

from igniteui-angularjs.

Merged: 20cf7b9

from igniteui-angularjs.