[Frontend] activity-content.tsx and incoming-content.tsx duplicate the same fetch/loading/error scaffolding with no shared hook

[grantfox-oss]

Join our community: https://t.me/+DOylgFv1jyJlNzM0

Why this matters

frontend/src/app/activity/activity-content.tsx and frontend/src/app/incoming/incoming-content.tsx both implement their own loading/error/empty-state handling around a data fetch, following the same shape. Duplicated scaffolding means a bug fix (e.g. an error-state edge case) has to be applied twice and can drift, exactly the kind of duplication already flagged for other pairs in this codebase.

Acceptance criteria

• Extract a shared useAsyncPageData-style hook or shared presentational wrapper for loading/error/empty states
• Migrate both pages to use it
• Confirm existing tests for both pages still pass

Files to touch

• frontend/src/app/activity/activity-content.tsx
• frontend/src/app/incoming/incoming-content.tsx
• frontend/src/hooks/

Out of scope

• Rewriting the data-fetching library used
• Changing the visual design of loading/error states

[Abdulrasaq1515]

I want to extract a shared hook for loading/error/empty states because activity-content.tsx and incoming-content.tsx both implement their own handling following the same shape. Duplicated scaffolding means a bug fix has to be applied twice and can drift. The fix extracts a shared useAsyncPageData hook (or presentational wrapper) and migrates both pages to use it.

Relevant experience:

Hook extraction — extracted shared data-fetching hooks for 3 React apps; loading/error/empty states

[Ajibose]

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

can i work on this work

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

[Enemuo-debug]

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

Can I please work on this?

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

[martinshub-tech]

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

I'd like to take this issue. I've analyzed the root cause and am confident I can deliver a reliable fix with proper testing

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

[Maximum-Prosper]

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

I'd like to contribute to this project.

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

[Michvista]

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

Please assign to me

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

[drips-wave]

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

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