enable restaurants working for some restaurants and not for others

Open
#1,377 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
javascript, react-native
Domain
mobile

Research direction

Start at the restaurants screen and trace the enable action, reproducing the failure for both a working and a failing restaurant in Chrome on Windows. Identify the difference between those cases and verify that the enable buttons work as directed for every affected restaurant.

Written by the indexing model from the issue text.

Description

Describe the bug
enable restaurants working for some restaurants and not for others

To Reproduce
Steps to reproduce the behavior:

Go to 'restaurants'
Click on 'enable'
See error
Expected behavior
buttons shall work as directed
Screenshots
image

Desktop (please complete the following information):

OS: Windows
Browser Chrome
Version 122.0.6261.95 (Official Build) (64-bit)

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

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.

More from raymondjames090/uber-eats-app-clone-using-react-native

All issues in raymondjames090/uber-eats-app-clone-using-react-native

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.