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
Is there a practical reason the StartOrCursor.Cursor has an internal constructor? I have a case where I'm exposing solr results through a rest api. I'd like to be able to return the next cursor and let the user send it back to me for the next page to do something like:
queryOptions.StartOrCursor =new StartOrCursor.Cursor([cursor string from request]);
but currently the only way to queryOptions.StartOrCursor is from a previous queryResult.NextCursorMark which can't be done through stateless requests.
The text was updated successfully, but these errors were encountered:
Is there a practical reason the StartOrCursor.Cursor has an
internal
constructor? I have a case where I'm exposing solr results through a rest api. I'd like to be able to return the next cursor and let the user send it back to me for the next page to do something like:but currently the only way to
queryOptions.StartOrCursor
is from a previousqueryResult.NextCursorMark
which can't be done through stateless requests.The text was updated successfully, but these errors were encountered: