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
The specification doesn't say how the start and count arguments to the variables query are supposed to interact with the filter argument:
With indexed filter, it's more-or-less obvious.
With named filter, not so much. Does filtering apply in this case at all?
Without a filter, it's even more underspecified. If paging applies to named variables, then how are variables supposed to be counted in case there are both? Should it essentially behave like there's one long list of both kinds of variables (but which of them come first then)? Or can they be arbitrarily interleaved?
With named filter, not so much. Does filtering apply in this case at all?
Coincidentally, a different part of the specification explicitly talks about paging named variables:
/** * The number of named child variables. * The client can use this information to present the variables in a paged * UI and fetch them in chunks. * The value should be less than or equal to 2147483647 (2^31-1). */
namedVariables?: number;
Activity
sim642 commentedon Jul 25, 2026
Coincidentally, a different part of the specification explicitly talks about paging named variables:
But that's under a completely unrelated request.