lambertf917 / lambertf917/ride-sharing-solution-react

Missing Record of Previous Orders in Enatega Multivendor Rider App.

Open
#276 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Issue: Missing Record of Previous Orders in Rider App
Description:
In rider app, there is currently no record of previous orders displayed. It is crucial to have a section that shows the rider's history of previous orders for reference and record-keeping.

Impact:
Order Tracking: The absence of a record of previous orders can make it difficult for riders to track their history and details of past deliveries.

Accountability: Previous order records are essential for accountability and resolving any issues related to past orders.

Steps to Reproduce:
Access the rider app.
Navigate through the app to find a section that displays the rider's history of previous orders.
Observe that there is no record of previous orders available.
Expected Resolution:
You need to implement a section in the rider app that shows a rider's history of previous orders. This will enable riders to track their deliveries and provide an essential reference point for resolving any past order-related issues.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The payload does not name a file, test, or entry point; start by locating the rider app's order and navigation screens, then trace how completed orders are retrieved. Done means the rider can open a section showing their previous orders with enough details for tracking and reference.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.