[FEAT] Implement Backend Infrastructure for Dishes

[ShivanshPlays]

Issue: Implement Backend Infrastructure for Dishes

Description

To manage dishes on the platform, we need a backend infrastructure that includes a Dish table in the database with a foreign key relation to the Vendor table. This setup will allow each dish to be associated with a specific vendor, enabling vendors to manage their specialized dishes directly. Additionally, backend server actions for Create, Read, Update, and Delete (CRUD) operations on dishes are required to allow full control over dish data.

Solution Steps

1. Define the Dish table schema with fields including:

example-

• id: Unique identifier for each dish.
• name: Name of the dish.
• description: Description of the dish.
• price: Price of the dish.
• vendorId: Foreign key reference to the Vendor table.
• Timestamps (createdAt, updatedAt).

2. Set up a foreign key constraint linking vendorId in the Dish table to the id field in the Vendor table.

3. Implement server actions for CRUD operations:

   • Create: Add a new dish linked to a specific vendor.
   • Read: Retrieve details of one or multiple dishes.
   • Update: Edit details of an existing dish.
   • Delete: Remove a dish from the database.

Acceptance Criteria

• [ ] Define Dish table in the database with a foreign key relation to Vendor.
• [ ] Implement CRUD server actions for dishes.
• [ ] Verify data integrity with foreign key constraints.

---

Checklist

• [ ] Define Dish schema and establish relation to Vendor table.
• [ ] Implement server actions for creating, reading, updating, and deleting dishes.

[github-actions[bot]]

🎉 Thank you for your interest in contributing to this repository! Please wait while we review and assign this issue to you. In the meantime, feel free to ⭐ the repo to stay updated on future developments.

Stay awesome! 😎