Backend Implementation for Delivery Person Management #994
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.
Overview:
This PR adds a backend solution for managing delivery personnel within the system, implementing features such as CRUD operations, status toggling, and consistent response handling. This functionality allows for seamless management of delivery personnel with validation, secure password handling, and error messaging.
Key Features:
1. Delivery Person Model Definition
DeliveryPerson
schema includes fields such asname
,email
,phone_number
,status
,assigned_routes
,vehicle_details
,profile_picture
, andpassword
.2. CRUD Operations
3. Status Toggling
4. Middleware Implementations
status
field5. Standardized Response Handling
6. Routing and Endpoint Definitions
POST /api/delivery-persons
: CreateGET /api/delivery-persons
: Retrieve all (paginated)GET /api/delivery-persons/:id
: Retrieve by IDPUT /api/delivery-persons/:id
: Update by IDDELETE /api/delivery-persons/:id
: Soft deletePATCH /api/delivery-persons/:id/status
: Status toggle