You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Pagination: describe page requests without a response continuation signal #25
The current pagination spec can declare a pageNumber request, but has no agreed description for deciding continuation solely from a result array length. Syncables derives continuation only from response token/link or counts and stops after the first page for this response. Its empty-page stop runs only after another continuation signal is present. Adding fabricated counts or an undocumented provider field would misdescribe the API. This blocks complete ClickUp task import and catalog activation.
Please discuss how the generic pagination specification should express APIs with incrementing page requests but no response continuation/count signal, and distinguish documented provider termination semantics from consumer traversal policy. Is a declared short/empty-page termination rule appropriate, and what evidence should be required when the provider only documents a maximum page size? This records the concrete gap; no new extension or provider-specific runtime workaround is proposed or implemented pending owner design feedback.
A second related representation gap: ClickUp page starts at0, while spec §4.5 defines request role page as1-based and Syncables starts it at1. Assigning this role to ClickUp would skip the first page even with a query default0 (the generated pagination query overrides it). The offset role is not an equivalent: the provider increments a page index by1, while offset advances by item count. An accurate generic design needs to represent the initial page index alongside response-less continuation, without reinterpreting the provider's page as an item offset. Prepared ClickUp metadata will omit an unsupported scheme rather than silently skip data; catalog activation remains held.
Activity
michielbdejong commentedon Oct 8, 2026
A second related representation gap: ClickUp
pagestarts at0, while spec §4.5 defines request rolepageas1-based and Syncables starts it at1. Assigning this role to ClickUp would skip the first page even with a query default0 (the generated pagination query overrides it). Theoffsetrole is not an equivalent: the provider increments a page index by1, while offset advances by item count. An accurate generic design needs to represent the initial page index alongside response-less continuation, without reinterpreting the provider's page as an item offset. Prepared ClickUp metadata will omit an unsupported scheme rather than silently skip data; catalog activation remains held.