Margaret-Petersen / Margaret-Petersen/uber-eats-clone-using-react-native

"Cancel Your Order" button should be hidden after order is assigned to rider, even if disabled

Open Beginner friendly
#1,765 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Describe the bug
Currently, once an order has been assigned to a rider, the "Cancel Your Order" button remains visible and disabled. To prevent user confusion and improve the interface, the button should be completely hidden after the order has been assigned to a rider, even if it remains disabled for some reason.

To Reproduce
Steps to reproduce the behavior:

Place an order through the app.
Wait until the order is assigned to a rider.
View the order details screen.
Notice that the "Cancel Your Order" button is disabled but still visible
Expected behavior
The "Cancel Your Order" button should be hidden from the order details screen once the order has been assigned to a rider, regardless of whether it is disabled.

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Add any other context about the problem here.

Labels: Enatega Multivendor Customer App, Bug

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

Start by locating the order details screen in the React Native app and trace how the "Cancel Your Order" button's visibility and disabled state are determined after rider assignment. Reproduce the assigned-order state, then verify that the button is absent from the screen regardless of its disabled state.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react-native
Domain
frontend, mobile
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.