Fix useApi infinite refetch loop caused by inline body/options object

[RUKAYAT-CODER]

Overview
In src/hooks/useApi.ts, fetchData (lines 47-78) lists body in its dependency array and the mount effect (lines 80-87) depends on fetchData. Because callers pass options/body as inline object literals, body's identity changes every render, recreating fetchData and re-firing the fetch on every render — an infinite fetch loop hidden by eslint-disable comments. Serialize deps (e.g. via a stable dedupe key) rather than relying on raw object identity.

[Nacho1499]

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

Hello Maintainer,I am Nacho, a full-stack developer, and I would love to contribute to the project.

I have reviewed the issue, and my approach would be:

1. Review src/hooks/useApi.ts and trace how fetchData, body, and options are currently used by callers.

2. Identify the unstable dependencies causing fetchData to be recreated whenever inline object literals receive a new reference during rendering.

3. Introduce a stable dependency strategy, such as generating a serialized or deduplicated key from the relevant request body/options, instead of relying on raw object identity.

4. Update the useCallback and effect dependencies so requests only re-run when the actual request data changes, not simply because an object gets recreated.

5. Preserve existing behavior for meaningful changes to the request body or options, ensuring legitimate updates still trigger a new fetch.

6. Test different usage scenarios, including inline objects, memoized objects, unchanged values across re-renders, and genuinely changed request data.

7. Remove or reduce any unnecessary ESLint dependency suppressions where the corrected dependency handling makes them unnecessary.

I would also verify that the fix prevents the infinite refetch loop without introducing stale data or missing legitimate updates.

I am confident I can provide a clean, focused fix that resolves the dependency issue while maintaining the intended behavior of the useApi hook.

If the issue is still available, I would really appreciate the opportunity to be assigned to it. Thank you for your time, and I look forward to contributing to the project!

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

[Olamidepy]

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

Hi Maintainer,

I would love to be assigned to this issue.

I’m a Full-Stack Developer and I also actively explore blockchain development and smart contracts, which has strengthened my problem-solving skills and attention to code quality.

After reviewing the issue, I believe I can contribute effectively and deliver a well-tested solution within the expected standards of the project.

ETA: 4 hours

Thank you for your consideration.

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

[solaawojobi00-bit]

@solaawojobi00-bit has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I'll add unit tests using ⁠@testing-library/react-hooks⁠ to ensure ⁠useApi⁠ only fires fetches when shallow/deep values change. Kindly assign it to me

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

[abdulqudus-dev]

@abdulqudus-dev has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

please ill like to work on this issue, assign it to me

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

[Mkalbani]

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

Hi maintainers, can I work on this. I've worked on a similar work. Thank you.

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

[drips-wave]

Congratulations, @Nacho1499! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@Nacho1499's PR #1243 was approved and merged by @RUKAYAT-CODER.

🏆 @Nacho1499: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (707 total points). Track your full progress on GrantFox.

👏 Great work, @Nacho1499! Keep contributing to rinafcode.

[drips-wave]

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

😎 @Nacho1499: 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.