Please provide link to gitlab issue or ADR(Architecture Decision Record)
The cursor is not being encoded, which is causing problems when making continuation queries.
The cursor value is encoded so the next time continuation queries need not worry about any encoding issues.
Yes, added unit test which otherwise did not cover for test coverage of the cursor flow of code.
Have initially started to use URLEncoding mechanism, but then discovered in the tests that Spring framework is already doing the decoding when the query param reaches to the handler. Again doing URLDecoding in the handler was causing data loss (it was removing
+ characters as it was assuming them to be encoded characters), so moved to basae64 encoding and decoding.