lambertf917 / lambertf917/food-ordering-system-source-code
Enatega Customer + Admin : Cuisine image is not showing default image, when no image is uploaded by the user
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Cuisine image is not showing default image, when no image is uploaded by the user. The default image should show up in case when no image is attached by the user.
AND
In restaurant screen there are some cuisines which have no images, when image is being add from admin then the cuisine is not being shown in the restaurant screen but its being shown on the home screen with image.
This issue is present in both ANDROID & IOS.
To Reproduce
Steps to reproduce the behavior:
- Go to 'Enatega Admin Dashboard'
- Click on 'Management' from menu and select cuisines from dropdown menu.
- Now click on +Add Cuisines button , add any cuisine.
- See error that default image is not showing up in it, its showing an random image with cuisines in Customer Application.
Expected behavior
The default image that is attached from backend should show up when no image is uploaded by user.
Screenshots
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 through the Enatega Admin Dashboard by adding a cuisine without an uploaded image, then check the Customer Application's restaurant and home screens on Android and iOS. Trace how the default backend image is selected and verify that the default image appears consistently and the cuisine remains visible in the restaurant screen.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100