-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
In almost all APIs (or at least the ones I implemented access to so far), the "count" field of a payload has always matched the number of items in the primary result array.
This enables basic payload validation ("is there a count, and does it match the number of items in this array?").
However, while the result of the sitewide artist statistics now pretty much match the result of the per-user artist statistics, the count returned is always 1000, not the actual number of results. It would be useful if this was changed to return the correct count in the "count" field. The user stats also have a "total_artist_count" field; perhaps the sitewide stats could/should also return that (and that would then always be 1000).
- is related to
-
LB-753 Align properties of statistics endpoint payloads
- Open