pagination module initializes ngModel to 1 if total-items starts out undefined

[AlJohri]

I'm grabbing metadata from an API where I know which page I would like to grab via the url parameters, but the total-items takes a few milliseconds to populate.

Because total-items starts out undefined, ngModel is changed from the correct page number to 1.

The only way I have gotten around this is to initialize total-items to an arbitrary number such as 1000. Then the page number is left alone.

Is there a better solution?

[chrisirhc]

This sounds like a bug. However, in order for me to verify and test the fix, I need a Plunker that demonstrates this issue. Do you mind creating an Plunker for this? You could use $timeout to simulate retrieval of the total-items.

[AlJohri]

http://plnkr.co/edit/M0UxBGHlB1vB6P1m5KL9?p=preview

ping @chrisirhc

[juanfran]

If I set currentPage at the same time that totalItems it works well

[brandonarbini]

+1, just ran into this. Not sure how to fix it or I'd submit a PR.

[wesleycho]

I am not sure if we want to change anything in the pagination here - what should num-pages return in this instance? How should the UI look?