Add integration test for activity feed showing correct creator handle for each trade entry

[Chucks1093]

Summary

Each entry in the wallet activity feed should display the creator's handle alongside the trade details. An integration test should confirm the correct handle is rendered for each entry and does not show a raw creator ID.

Scope

• Render the activity feed with two trade entries from different creators
• Assert each entry displays the correct creator handle
• Assert no raw creator ID number is visible to the user

Acceptance Criteria

• Each entry shows the correct creator handle
• Raw creator ID not visible in the rendered output
• Two entries from different creators show different handles

ETA: 12 hours

---

Coordinate on Telegram

[taiwoMoil]

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

Hello, I’d like to take this issue and contribute a fix. I’m familiar with the technologies involved and will investigate the problem before creating a pull request. Looking forward to contributing to the project.

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

[NickiM84]

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

Hello, I'm a fullStack developer with years of experience, I have worked on several projects, can I please work on this.

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

[AlphaMaleBaDI]

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

Hi Maintainers, I will solve this by adding an integration test for the activity feed ensuring the correct creator handle is displayed for each trade entry within the accesslayerorg/accesslayer-client repository.

To deliver a pristine, 100% compliant frontend verification layer matching all stated acceptance criteria, I plan to:

• Construct an integration test suite targeting the wallet activity feed component rendering lifecycle.
• Seed or mock the test context with exactly two independent trade entries originating from two distinctly different creators.
• Assert that the rendered output successfully resolves and displays the human-readable creator handle for both entries.
• Explicitly verify that no raw creator ID numeric values or fallback strings are exposed anywhere within the visible document tree to ensure polished presentation and privacy compliance.

Since my local workspace is perfectly calibrated for frontend integration testing frameworks, mock data lifecycle contexts, and client-side feed rendering assertions, I can jump straight into the test environment and submit a highly polished PR immediately. Ready to lock it in!

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

[kingbitnation]

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

Hi! I'd like to work on this issue.

After reviewing the requirements, I believe it's a good match for my experience. I'll implement the requested functionality while following the project's existing architecture, coding conventions, and contribution guidelines. I'll ensure the solution is clean, well-tested, and covers all of the stated acceptance criteria, updating or adding tests where appropriate and documenting any relevant changes.

If I encounter any implementation details that need clarification, I'll communicate them early to avoid unnecessary rework.

Could this issue be assigned to me?

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

[chukwuebuka19]

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

Hello I would love to work on this and get it done ASAP

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

[drips-wave]

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

🧑‍💻 @kingbitnation: 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 🌊