Now that the search endpoint handles cursorMark, we should be able to introduce a cursor=true parameter, and then have the library automatically create a .next() function that continues to traverse the stack.
This would be preferred over the dirty way I threw together at https://gist.github.com/ecaron/1e4851492d58db66ef4c1ef53010234a
Now that the search endpoint handles cursorMark, we should be able to introduce a cursor=true parameter, and then have the library automatically create a .next() function that continues to traverse the stack.
This would be preferred over the dirty way I threw together at https://gist.github.com/ecaron/1e4851492d58db66ef4c1ef53010234a