@community(@instances) that are non exising not correctly handled
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1.3k
- Forks
- 175
- Avg merge
- 6d 22h
- Merged PRs (30d)
- 9
Description
Jerboa Version
Latest from main
Describe the bug
Clicking on a community that doesnt exist still tries to open a view for that community but then gives an error text and the scroll is than frozen, not sure what it is even displaying. It should either not redirect to that community and say community doesnt exist. or like a templatish thing with default image that community name and some text that says this community doesnt exist yet.
To Reproduce
Click on a @community that doesnt exist yet.
Video of the problem
https://github.com/dessalines/jerboa/assets/67873169/5472e30f-1349-4403-9955-448d5b5d3d49
Unrelated (i think) this community actually exists, https://lemmy.ca/c/trippinthroughtime
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 reproducing the issue by opening a nonexistent @community in Jerboa and trace the community navigation and view handling from that interaction. Done means the app either avoids redirecting or shows a clear nonexistent-community state without an error or frozen scrolling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100