dir-paginate fails to properly update when used with ng-if

[dougpool]

I noticed when I tried to use the dir-paginate directive on an element that was a child of a div that was conditionally show using ng-if, the dir-paginate did not properly display. When ng-if was replaced with ng-show, the dir-paginate directive worked normally.

Sample structure where dir-paginate appears to not work correctly.

<div ng-if="someCondition()">
<div dir-paginate="item in items | itemsPerPage:someNumber ....>{{item}}</div>
</div>

[michaelbromley]

Yeah, you're right. I think it has to do with the fact that ng-if creates its own scope, but I've not got to the bottom of why it behaves the way it does.

I'll need to spend some more time on this when I get the chance. In the mean time, if anyone wants to take a look into it, here is a Plunk of the failing case: http://plnkr.co/edit/W7YYxJ?p=preview

Here is a discussion about how ng-switch creates a new scope (which also applies to ng-if) in which Misko Hevery explains why that is: http://plnkr.co/edit/W7YYxJ?p=preview

[callmekatootie]

I face the same issue with ng-switch though. I played around with the plunkr and found that even if a new scope exists within the ng-if, it does not work - Here's my plunkr fork. I moved the controller just above the directive and the ng-if directive is above the controller.

My understanding is that the controller scope is within the ng-if and thus the directive and the controller are working on the same scope. Or I may have misunderstood scopes and this is still the same issue.

[michaelbromley]

This issue is now fixed with update 716ac51

See issue #37 for an explanation if you are interested.