Great point about adding total record counts to GET responses—it really improves clarity for anyone working with paginated data. Knowing the full scope upfront helps with better UI decisions and reduces unnecessary follow-up requests. I’ve seen similar ideas applied when browsing large public datasets, such as through resources like https://hillsboroughcountycourts.org where context around volume makes navigation far more intuitive. Overall, this approach feels practical and developer-friendly, especially for data-heavy applications.
Great point about adding total record counts to GET responses—it really improves clarity for anyone working with paginated data. Knowing the full scope upfront helps with better UI decisions and reduces unnecessary follow-up requests. I’ve seen similar ideas applied when browsing large public datasets, such as through resources like https://hillsboroughcountycourts.org where context around volume makes navigation far more intuitive. Overall, this approach feels practical and developer-friendly, especially for data-heavy applications.