Summary

Adds TSDoc clarification to the select() method explaining that count with pagination methods returns the total number of matching rows, not the paginated count.

Problem

Users reported that count appears to "ignore" .range() filters, expecting count to match data.length when using pagination. However, this is the intended behavior, not a bug.

The confusion arises because:

• data.length returns the number of rows in the current page (e.g., 10)
• count returns the total number of matching rows across all pages (e.g., 100)

Solution

Added @remarks to the select() method TSDoc clarifying that when using count with .range() or .limit(), the returned count represents the total number of rows matching your filters (before pagination).
This is the intended behavior to enable building pagination UI like "Showing 1-10 of 100 results".

Related

• Closes SDK returns incorrect value of count but data correctly filtered by range() and is() #1275

Summary by CodeRabbit

• Documentation
  • Clarified documentation for count operations when used with pagination or limit parameters, specifying that the count reflects the total number of rows matching filters rather than just the returned subset.

_{✏️ Tip: You can customize this high-level summary in your review settings.}