Use DRF 3.1 pagination_class

[humitos]

Closes #3251

[humitos]

@ericholscher @agjohnson since we were talking that mixing style and logic PR is kind of tedious, I created another PR based on this where I ran pre-commit on the modified files and tweaked a little manually.

Let me know if you like this approach. It a little tedious to make two different PR but I hope it simplies the review.

[safwanrahman]

I think, rather than fixing from the backend, this should be controlled by page_size parameter from the frontend. what do you think @humitos ?

[humitos]

@safwanrahman good catch!

I think it's a good idea. I'd like to fix the bug and make it work as it was working before since it could be other places that use that endpoint and may rely on that pagination size also.

From #3251

I think there should be a button in the UI for going next

Yes, we should think in a non-intrusive UI design for this. Most of the users won't have more than 25 organizations (in fact we have just one report of a person having 11 :) ).

But anyway, I agree with both suggestions but I'd like to make them in different PR.

If you agree with me, would you mind openning these two issues? Thanks!

[ericholscher]

Looks good to me for the immediate fix. We can let users set a page size in the future, but at least having working pagination is a good step :)

Might be useful to include a test, so that if it breaks again, we'll know.

[safwanrahman]

I think you can get the url by using reverse. So it will be easier to manage in the future

[safwanrahman]

Looks good.
I have a minor correction, but its ok to ignore that and handle in future