marthaegrimaldi / marthaegrimaldi/ifood-clone-using-react-native

Enatega Customer Application : On Checkout screen the Instruction for restaurant message heading is incorrect check screenshots

Open
#285 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
On the Checkout screen, the heading for the "Instruction for Restaurant" message is incorrect. Instead of displaying instructions for the restaurant, it is showing the message intended for the courier.

To Reproduce
Steps to reproduce the behavior:

Go to 'Enatega Customer Application'
Place an order.
Now see error , insert any special instructions for the restaurant at your cart screen now On the Checkout screen, the heading for the "Instruction for Restaurant" message is incorrect. Instead of displaying instructions for the restaurant, it is showing the message intended for the courier.

Expected behavior
The heading should correctly indicate that the message is for the restaurant.

Smartphone (please complete the following information):

Device: [e.g. Infinix Hot 50]
OS: [e.g. Android]
Browser [e.g. Application]
Version [e.g. Latest]

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 in the Enatega Customer Application's Checkout screen and trace the restaurant-instruction heading shown after adding special instructions from the cart. Reproduce the checkout flow, correct the heading so it identifies the restaurant rather than the courier, and verify the displayed message matches the expected behavior.

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
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.