Margaret-Petersen / Margaret-Petersen/uber-eats-clone-using-react-native
Enatega Customer Application + Admin : The default food should not be create or shown on customer application and admin side
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When the new store is created there shouldn't be any default food already created or category and it shouldn't be shown on customer application.
To Reproduce
Steps to reproduce the behavior:
Go to 'Enatega Customer Application'
Click on Store
Scroll down to 'Category'
See error
Expected behavior
There should not be any already created default food or any category.
Screenshots
Image
Smartphone (please complete the following information):
Device: [e.g. Infinix Hot 50 ]
OS: [e.g. Android ]
Browser [e.g. Application]
Version [e.g. 14]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in the Enatega Customer Application by opening a store and checking its Category section, then inspect the related store and category flows in the customer and admin applications. Done means a newly created store has no default food or category and neither application displays one automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- frontend, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100