React Appointment Scheduler Bug Fix
Budget: ₹100 – ₹400 INR
My React-based appointment platform is almost ready to ship, but two stubborn issues in the scheduling logic are blocking release:
• The time-slot generator sometimes shows options that should be unavailable.
• When a user hits “Book,” the request hangs far longer than it should.
I need a developer who can dive straight into the existing React frontend (hooks and context), trace the slot-generation flow through to the scheduling API, and deliver a clean, well-tested patch. You’ll verify that only legitimate slots appear under every timezone/working-hours scenario and profile the booking call so the confirmation returns promptly.
Deliverables (acceptance criteria)
1. Updated logic that always publishes correct, conflict-free time slots.
2. Booking operation completes in a consistently snappy timeframe (ideally under 2 seconds on a standard connection).
3. Brief change log plus any schema or endpoint tweaks documented for my team.
I have the repo on GitHub and can spin up a staging instance for testing. Once the fix is merged, we’ll run a quick regression test, and I’ll sign off immediately.
• The time-slot generator sometimes shows options that should be unavailable.
• When a user hits “Book,” the request hangs far longer than it should.
I need a developer who can dive straight into the existing React frontend (hooks and context), trace the slot-generation flow through to the scheduling API, and deliver a clean, well-tested patch. You’ll verify that only legitimate slots appear under every timezone/working-hours scenario and profile the booking call so the confirmation returns promptly.
Deliverables (acceptance criteria)
1. Updated logic that always publishes correct, conflict-free time slots.
2. Booking operation completes in a consistently snappy timeframe (ideally under 2 seconds on a standard connection).
3. Brief change log plus any schema or endpoint tweaks documented for my team.
I have the repo on GitHub and can spin up a staging instance for testing. Once the fix is merged, we’ll run a quick regression test, and I’ll sign off immediately.
Related categories:
JavaScript
Amazon Web Services
HTML
Node.js
Express JS
Git
React.js
API
Frontend Development
RESTful API