Missing page: Orders (/orders)

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
react, typescript
Domain
frontend

Research direction

Start by locating the existing React Router setup and the navigation and footer links that point to /orders. Then inspect how the application represents user orders and handles authentication before planning the Orders component and individual order details. Done means /orders is reachable, displays the required order information and empty state, supports filters or sorting, and the links no longer use #.

Written by the indexing model from the issue text.

Description

Problem

The /orders route is not implemented in the application. When users try to navigate to /orders, they see an empty page with a console warning: "No routes matched location '/orders'"

Expected Behavior

Users should be able to view their order history, including:

  • List of all orders with order number, date, and status
  • Order details (items, quantities, prices)
  • Order status tracking
  • Ability to view individual order details

Current Behavior

  • Navigation to /orders shows an empty page
  • Console warning: "No routes matched location '/orders'"
  • Footer links to "Order" use placeholder "#" href

Acceptance Criteria

  • Create /orders route in React Router
  • Implement Orders component to list user's orders
  • Display order number, date, status, and total for each order
  • Add ability to click on order to view details
  • Show "No orders yet" message for new users
  • Add filters/sorting options (by date, status)
  • Update navigation/footer links to point to /orders
  • Consider authentication requirement

Priority

Medium - Important for user experience and order tracking

Dominant language
TypeScript
Stars
66
Forks
38
Avg merge
21d 15h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

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.

More from microsoft/GitHubCopilot_Customized

All issues in microsoft/GitHubCopilot_Customized

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.