4 Open Issues Need Help Last updated: Jul 6, 2025

Open Issues Need Help

View All on GitHub
ft/020_Categories about 2 months ago

AI Summary: Implement Create, Read, Update, and Delete (CRUD) operations for a 'Category' entity, and establish a relationship between 'Category' and 'Restaurant' entities. This likely involves creating controllers, services, repositories, and DTOs for the Category entity, and updating the Restaurant entity to include the category relationship (likely a many-to-one or one-to-many relationship).

Complexity: 3/5
help wanted Easy_Issue
ft/011_Dashboard_For_All about 2 months ago

AI Summary: Develop a REST API endpoint (`/dashboard`) that retrieves dashboard data for different user roles (Customer, Delivery, Restaurant Owner, SuperAdmin). The endpoint should fetch data from multiple tables (menu, order_data, restaurant_data, delivery_data, user_data) and tailor the response based on the user's role. This involves data aggregation and potentially role-based access control.

Complexity: 4/5
help wanted Complex_Issue
ft/001_LoginSignUp about 2 months ago

AI Summary: Implement user authentication and registration features for a food ordering system. This includes login and signup endpoints for restaurant owners, customers, and delivery staff, along with password reset and OTP confirmation functionalities. The implementation should follow the project's existing layered architecture and utilize existing DTO structures for responses.

Complexity: 4/5
help wanted Complex_Issue

AI Summary: Implement API endpoints for a SuperAdmin to manage users. This includes GET endpoint to retrieve all users with pagination and advanced search capabilities, and a DELETE endpoint to soft-delete users by ID. The implementation should follow the project's existing layered architecture and utilize existing components like DTOs, repositories, and services. Error handling and appropriate HTTP status codes are required.

Complexity: 4/5
good first issue