Change page again before async request is complete

I’m not sure if this is a bug or a problem on my side. When I double click either side of three dots, I get an infinite loop of some kind.

1. When you click a page number: that number becomes active, shifts to left or to right synchronously, makes a request async.
2. When you click a page number again: same as above.
3. Request that was made by point 1) resolves. It updates data, current page, page size etc. At this point, current page in pagination control and current page of the request are different so there is some kind of a clash?
4. Request that was made by point 2) resolves.

I cannot share any code. But I have an idea about the difference between common use case and my use case: I update current page and page size after each request.

So as a workaround, I want to disable pagination control during a request. Any suggestions? I don’t think there’s an ng-disabled on the pagination control.

Obviously I can do it inside on-page-change handler, I was just wondering if there’s any way to apply “disabled” style to the whole element.

[anilanar]

I made this commit as a quick fix to my situation. If you like the idea of having an ng-disabled attribute on the control, I can add tests, update docs etc. and make a pull request.

[stephanbarrett]

@Eduardoluisgm I implemented what @anilanar committed and it works well.