Wishlist Backend Implementation: schema, server actions, API #264
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.
Wishlist Backend Implementation
Summary
This pull request introduces the backend infrastructure for managing Wishlists within the application. It adds schema definitions, server actions, and API endpoints necessary to support Wishdish functionality for customers, allowing them to save dishes.
Changes Overview
Database Schema:
Wishlist
model to create a many-to-many relationship betweencustomer
anddish
.Server Actions:
actions/customer
folder to handle Wishdish operations.API Endpoints:
/api/Wishlist/:customerId/:dishId
- Adds a Wishlist for a specific customer and dish./api/Wishlist/:customerId/:dishId
- Removes a Wishlist./api/Wishlist/:customerId
- Retrieves all Wishlists for a customer./api/Wishlist/exist/:customerId/:dishId
- Checks if a Wishlist exists for the given customer and dish.Testing
tested all endpoints
Additional Notes
This PR is ready for review. Please check for adherence to backend standards and consistency with the overall project architecture.
1.mp4
PR2 #242