after cursor: empty value sometimes OK, sometimes not #24443
-
Hi there, A bit baffled by what I’m experiencing, hopefully I’m missing something. In a nutshell, I have 2 queries, one to get tags on a repo and another one to perform a search. Both of them implement pagination and as such I have to pass the afterCursor parameter. On the first call since there’s no afterCursor I simply pass a blank string and it works for tags but not for search:
yields expected results, while
yields error “type”: “INVALID_CURSOR_ARGUMENTS”, “message”: “`` does not appear to be a valid cursor.” Do acceptable values for afterCursor depend on the connection? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Have you tried |
Beta Was this translation helpful? Give feedback.
-
Making $afterCursor a String (not String!) and passing a null works! Thanks!! |
Beta Was this translation helpful? Give feedback.
Have you tried
null
instead of a blank string? It’s possible that the implementation slightly varies, yes. You may also want to try using two copies of the query, one with theafter
parameter and one without.