Improve handling of Server issues/disconnected
Open
Nobody has claimed this yet.
client: 💻 desktop
client: 🤖🍏 mobile
design
feature: conversations 👥
feature: frontend 🖌️
overview
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
During the team week we discussed various improvements that can be done on various clients
- "Connecting / Loading" 3px bar at the top of conversation list or top bar, when starting 🖱️🖌️🍎🤖
- Tiny information when no internet connection 🖱️🖌️🍎🤖
- Tiny information when server is 502 (turn of server) or 503 (maintenance/update) 🖱️🖌️🍎🤖
- Tiny information when server is slower than usual 🖱️🖌️🍎🤖
- Admin disable option
- Median over as many days as we can hold
- Dashboard when first loaded is completely empty and should say "Server not reachable" 🖱️🖌️
- Don't offer "Delete account" as first option (when not reachable since recently) 🤖 https://github.com/nextcloud/talk-android/issues/5038
- Inform when scrolling to the top and reaching the end while still not connected 🖱️🖌️🍎🤖
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 by reviewing the issue's requested connection, offline, 502/503, slow-server, empty-dashboard, and end-of-list states, noting the client targets marked in the body. Compare the linked Android issue for the account-deletion case; done means agreeing on scope and implementing consistent feedback for the selected clients.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100