-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Labels
BackendBackend TicketBackend Ticket
Description
Routes Domain Enhancement Proposal
Overview
This document outlines the proposed enhancements for the Routes domain in our backend architecture, focusing on the creation of a Route model and the development of CRUD operations.
1. Route Model Development
Features:
- One-to-Many (o2m) Relation to Attraction: Each route can link to multiple attractions, allowing for a diverse and rich travel experience.
- Many-to-Many (m2m) Relation to User: This relationship facilitates route sharing among users, promoting community interaction and route collaboration.
- Generated ID: A unique identifier for each route, ensuring easy management and referencing.
- Route Name: A field to store the name of the route, providing a personal touch and easy identification.
2. CRUD Operations
Functionalities:
- Adding/Removing Attractions: Users can dynamically modify their routes by adding new attractions or removing existing ones.
- Creating and Deleting Routes: Users have the ability to create fresh routes and also delete any they no longer need.
- Route Retrieval: Functionality for users to view and explore the details of existing routes.
- Route Updating: Users can update their routes, including changing the route's name or modifying the order and selection of attractions.
Goal:
These enhancements aim to establish a robust and user-friendly Routes domain, ensuring scalability and maintainability for future features such as advanced route customization and sharing functionalities.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
BackendBackend TicketBackend Ticket