Add unit tests for cursor encoding and decoding helper used in paginated endpoints

[Chucks1093]

Summary

The cursor encoding helper (base64 encode/decode of pagination metadata) is used across all paginated endpoints but has no unit tests. Tests should confirm round-trip correctness and safe handling of edge cases like empty cursors and malformed input.

Scope

• Test encode followed by decode returns the original value for a standard cursor object
• Test decoding an empty string returns null without throwing
• Test decoding a non-base64 string returns null without throwing
• Test cursor object with special characters (spaces, slashes) survives the round trip

Acceptance Criteria

• Encode → decode round trip is lossless
• Empty string decodes to null
• Invalid base64 decodes to null without error
• Special characters in cursor values survive round trip

ETA: 12 hours

---

Coordinate on Telegram

[OkeQueen]

@OkeQueen has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi Chief Maintainer, I'd like to work on this if it's still available.

I've read the issue and have a reasonable understanding of the work involved. I'd start by reproducing the behavior locally and confirming it still occurs on main, then work back to the underlying cause before making any changes.

The PR would include tests for the described case, a check that existing behavior is unaffected, and documentation updates where relevant.

I'll follow the repo's contribution guidelines and keep this thread updated. If I run into anything ambiguous, I'll ask here rather than guess and go in the wrong direction.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @OkeQueen to this issue.

[ieshasking01]

@ieshasking01 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello, I’ve gone through the issue details and I’m ready to begin working on it. I’ll ensure the final solution aligns with the project’s standards and requirements.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ieshasking01 to this issue.

[Isihaq123]

@Isihaq123 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

hey i will like to work on this issues

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Isihaq123 to this issue.

[abayomicornelius]

@abayomicornelius has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Please let me work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @abayomicornelius to this issue.

[drips-wave]

Congratulations, @abayomicornelius! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @abayomicornelius: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @abayomicornelius as part of the Stellar Wave Program's 7th Wave 🥳

😎 @abayomicornelius: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.