lambertf917 / lambertf917/react-native-uber-eats-clone

Enatega Customer Application : In Restaurant info , restaurant and Website infront of them its written none

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

Nobody has claimed this yet.

bug Enatega Multivendor Customer App good first issue
Dominant language
JavaScript
Stars
3
Forks
5
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
When we open a restaurant details card and click on its info icon all of its necessary details will open up and at the bottom of screen there is written Restaurant none and Website none so either allow user on admin dashboard store profile to enter the restaurant name field and its website field or there should be no such headings.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Enatega Customer Application'
  2. Click on 'Restaurant card details'
  3. now click on the top right corner Info icon , restaurant details will open up see at the bottom of screen the two headings Restaurant and Website.

Expected behavior
so either allow user on admin dashboard store profile to enter the restaurant name field and its website field or there should be no such headings.

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 by reproducing the issue in the Enatega Customer Application: open a restaurant card, then use the top-right Info icon and inspect the restaurant details screen. Trace that screen to determine whether the Restaurant and Website values come from the admin store profile or are rendered unconditionally; done means the details screen no longer displays unusable “none” headings, with the chosen behavior covered by a relevant test if one exists.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react-native
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.