Enatega Admin Dashboard: Remove Image upload orientation error, showing up once user uploads a wrong image size
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start in the Enatega Admin Dashboard image upload sections for the Store, Vendor, and Cuisine pages, and reproduce the issue with an image that does not meet the expected size. Done means images of any size are accepted and no orientation error is displayed.
Written by the indexing model from the issue text.
Description
Describe the bug
Unnecessary orientation error appears when a user uploads an image with an incorrect size. Allow the User to upload image of any size no restrictions for image orientation.
To Reproduce
Steps to reproduce the behavior:
- Go to 'Enatega Admin Dashboard'.
- Navigate to the image upload sections on Store, Vendor, Cuisine pages.
3.Upload an image that does not meet the expected size requirements.
4.Observe the error message displayed, remove that restriction and error message also.
Expected behavior
The system should accept images of any size.
No error should be shown regarding image orientation.
Desktop (please complete the following information):
- OS: [e.g. Windows]
- Browser [e.g. Chrome]
- Version [e.g. Latest]
Describe the bug
Unnecessary orientation error appears when a user uploads an image with an incorrect size. Allow the User to upload image of any size no restrictions for image orientation.
To Reproduce
Steps to reproduce the behavior:
- Go to 'Enatega Admin Dashboard'.
- Navigate to the image upload sections on Store, Vendor, Cuisine pages.
3.Upload an image that does not meet the expected size requirements.
4.Observe the error message displayed, remove that restriction and error message also.
Expected behavior
The system should accept images of any size.
No error should be shown regarding image orientation.
Desktop (please complete the following information):
- OS: [e.g. Windows]
- Browser [e.g. Chrome]
- Version [e.g. Latest]
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from patriciaperez90/react-native-based-uber-eats-clone-app
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
patriciaperez90/react-native-based-uber-eats-clone-app#2622 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
patriciaperez90/react-native-based-uber-eats-clone-app#2620 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
patriciaperez90/react-native-based-uber-eats-clone-app#2564 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patriciaperez90/react-native-based-uber-eats-clone-app#2558 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patriciaperez90/react-native-based-uber-eats-clone-app#2557 ·
All issues in patriciaperez90/react-native-based-uber-eats-clone-app
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100