[WIP] Make paginator definition explicit #33
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are cases when both will_paginate and kaminari will be in your dependencies, even though you're only using one of them. In our case we're using will_paginate and activeadmin (which internally uses kaminari for pagination).
I've modified the way ApiPagination initializes to allow explicit paginator definition. It works like this:
initializers/api_pagination.rb
This way you can have both kaminari and will_paginate defined and still be able you use this gem for api pagination.
You do loose the ability to just include the gem in the gemfile and be done with it (now you also need to define an initializer).
It should be possible to have both, what do you think about this workflow?