No API rate limit handling in backend.ts

[ritaifeoluwa]

What changed

• src/lib/backend.ts makes API calls to smartdrop-backend without handling 429 rate limit responses
• If the backend rate limits the frontend, users see generic errors

Why

• Should detect 429 responses and show a "rate limited — try again in X seconds" message
• Could also implement client-side request queuing

How to test

1. Check src/lib/backend.ts for 429 handling
2. Confirm no retry-after or rate limit logic

[achebejohnpaul]

Am a full-Stack Engineer focused on frontend, backend, APIs, automation, and modern web technologies. Passionate about solving real-world problems, contributing to open source, and delivering clean, scalable, review-ready solutions.

[achebejohnpaul]

Am a full-Stack Engineer focused on frontend, backend, APIs, automation, and modern web technologies. Passionate about solving real-world problems, contributing to open source, and delivering clean, scalable, review-ready solutions.

[achebejohnpaul]

Am a full-Stack Engineer focused on frontend, backend, APIs, automation, and modern web technologies. Passionate about solving real-world problems, contributing to open source, and delivering clean, scalable, review-ready solutions.

[achebejohnpaul]

Am a full-Stack Engineer focused on frontend, backend, APIs, automation, and modern web technologies. Passionate about solving real-world problems, contributing to open source, and delivering clean, scalable, review-ready solutions.

[ghzhost]

Submitted PR #330 addressing this issue with 429 rate limit detection, retryAfterSeconds support in BackendApiError, dynamic TanStack Query retry delays respecting Retry-After, and comprehensive unit tests.

[rupesh-kumar-sah]

Hi everyone,

I can tackle No API rate limit handling in backend.ts. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in SmartDropLabs/smartdrop-frontend
• Core Implementation: Build No API rate limit handling in backend.ts with clean React/Next.js components, responsive styling, and proper loading/error boundaries.
• Quality Assurance: Add component unit tests and ensure zero TypeScript/ESLint warnings.

Looking forward to contributing—please feel free to assign!