Feat: Connected frontend pages to live API with full loading state handling #30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📌 Feat: Connected frontend pages to live API with full loading state handling
📝 Summary
This PR integrates live API data fetching into the frontend and improves the backend to support it.
Previously,
/my-bookings,/rooms, and/rooms/:idwere using static dummy data.Now, these pages fetch data dynamically from the backend and handle all request states (loading, empty, error, success).
✅ Changes Made
Frontend
MyBookings.jsxto fetch live data from/api/bookings.AllRooms.jsxto fetch live data from/api/rooms.RoomDetails.jsxto fetch live data from/api/rooms/:id.Backend
GET /api/rooms– returns all roomsGET /api/rooms/:id– returns single room detailsGET /api/bookings– returns user bookingsserver.jswith new routes, improved error handling & CORS.clerkWebhooks.jswith better validation, logging, and error handling.🧪 Testing
🚀 Screenshots (Optional)
📌 Additional Notes
AllRoomswith API query params.RoomandBookingshould be fully implemented to serve actual DB data.🔗 Issue Reference
Closes #20