Fix records_count when using group by #49
+13
−1
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.
Changes
records_count
to handle hashes (typically returned withgroup
). As it stands, onlyActiveRecord_Relation
are handled. This fix ensures an integer is always returned.count
tosize
to avoid any misleadings / documentation collisions.Detail
Currently, when using
select
to load custom attributes that are grouped on the Model, thecount
breaks when evaluating@page.last?
. Specifically, this breaks onwhile residual > 0
with the error ofno implicit conversion of Integer into Hash
.After looking at the
method-i-count
docsThis explains the quirk.
Example usage: