lambertf917 / lambertf917/food-ordering-system-source-code
Enatega Customer Application : Add a pull down refresh loader on all screen while there is an internet connectivity issue.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
On restaurant screen and discovery screen, when the internet connection is lost these screens showing a still message 'Something went wrong'. There add a pull down refresh loader to reload the content.
To Reproduce
Steps to reproduce the behavior:
- Go to 'Enatega Customer Application'
- Now turn off the wifi.
- See error , the screen with a still message 'Something went wrong'.
Expected behavior
- Pull-Down Refresh Gesture:
Users should be able to swipe down on the screen to trigger a refresh.
A loader/spinner should appear, indicating that the app is attempting to reload content.
- Retry Fetching Data:
On pull-down, the app should check the internet connection and attempt to reload the restaurant and discovery data.
Error Handling:
If the internet is restored, the content should load successfully.
If the connection is still lost, an updated message (e.g., "No internet connection. Pull down to retry.") should be displayed.
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
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
Start in the Enatega Customer Application by reproducing the issue on the restaurant and discovery screens with Wi-Fi disabled. Inspect how those screens display the “Something went wrong” state and how content is fetched. Done means pull-down refresh shows a loader, retries the data fetch, loads content after reconnection, and shows an updated retry message when offline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100