Strategy for grouped resources

I realize this isn't exclusively a JR question, but I feel it's too common to not bring it up and how one might accomplish it using JR.

My current use case has a type of model that's the basis for summed queries grouped by one or more attributes. In this case, it's a timesheet entry, and I initially need to group them by user_id and project_id, but they could easily be grouped by time periods as well. The aggregated value is SUM(hours). I've created an TimesheetEntryCollection model as an ActiveModel::Model object to handle the aggregated data, but I'm unsure how to serialize them, as JR expects and ActiveRecord::Relation to be returned from the Resource's self.records method and I'm not sure how to force a relation out of a tableless model. Do I just need to override the controller methods, or is there some way to do this through the resource?

Am I thinking about this the wrong way? Should JR maybe allow arrays to be returned from self.records with the understanding that you have to handle pagination/filtering yourself?

Any help would be greatly appreciated!

Commencez par le contrat self.records de Resource et les méthodes du contrôleur mentionnées dans le rapport, puis suivez la manière dont JR sérialise une ActiveRecord::Relation. Comparez ce chemin avec le ActiveModel::Model sans table TimesheetEntryCollection et le cas d’utilisation de SUM(hours) groupé. La tâche est terminée lorsqu’une approche est convenue pour les ressources groupées, notamment pour déterminer si les arrays et la pagination ou le filtrage gérés par l’appelant sont pris en charge.