When the resources query is called with a filter, it would be useful to have the totalCount returned in addition to the filtered count.
Alternatively, we could stick with one value, count and say it always represents the total, and ignores the filter. This would be consistent with how the query works now when the count is higher than the limit. Only limit items are returned, but the count tells you the actual total.
Essentially, i need to know that filter: xxx matched 8 out of 9,743 items.
When the
resources
query is called with afilter
, it would be useful to have the totalCount returned in addition to the filtered count.Alternatively, we could stick with one value,
count
and say it always represents the total, and ignores the filter. This would be consistent with how the query works now when the count is higher than thelimit
. Onlylimit
items are returned, but thecount
tells you the actual total.Essentially, i need to know that
filter: xxx
matched 8 out of 9,743 items.