entriesForParticipantCount
Query
How many entries entriesForParticipant would match for the same arguments,
ignoring limit / offset (POD-619).
The list is capped — limit defaults to the deploy’s list page size — and carries
no total, so a short page and a complete history are indistinguishable to a caller.
A client that pages (or that wants to say how much it is NOT showing) needs this to
tell the difference. Accepts the same filters as the list so the number always
describes the list you would get with those arguments; both share one predicate
builder server-side, so the two cannot drift apart.
A sibling field rather than a totalCount on a wrapper type: entriesForParticipant
returns [Runner!]! and is customer-facing, so reshaping it into a result object
would break every existing consumer.
Alias-aware like the list (RAC-9858): counts entries across the participant’s whole merge cluster.
Returns: Int!
Arguments
Section titled “Arguments”| Name | Type | Description |
|---|---|---|
entityType | ParticipantEntityType! | — |
participantId | ID! | — |
futureOnly | Boolean | Mirrors the list argument: restrict to races at or after now, excluding finished races and inactive entries. |
pastOnly | Boolean | Mirrors the list argument: the complement of futureOnly — exact when withinDays is unset. Mutually exclusive with it. |
withinDays | Int | Mirrors the list argument: upper bound on the future window in days. Only applies when futureOnly is true; must be an integer 1–365. |
excludeStatuses | [RunnerStatus!] | Mirrors the list argument: entry statuses to exclude from the count. |