Discovery cannot click into the subrouter lev
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- android, typescript
Research direction
Start by reproducing the problem in the Android Discovery tab: open a router with subrouters and try selecting each child. Compare the RSS hub API requirements with the request data passed by Folo, especially for subrouters that fail. Done means every displayed subrouter opens successfully without breaking the working cases.
Written by the indexing model from the issue text.
Description
Platform
Mobile - Android
Describe the bug
As described on the title, I cannot click into the sub-router of each router displayed in the discovery page. There seems to be a mismatch between the RSS hub's API requirement and what has been passed from the folo.
The way to reproduce this is quite simple. You just try to click into the discovery tab and then click some router that has their sub router and then try to click into one of them.
However this problem has only been discovered on some of the subrouters, so I don't know what's the mechanism behind it. Might be not properly defined router interface.
Entry ID
No response
Relevant Information
No response
Reproduction Video
https://github.com/user-attachments/assets/4400a94e-f6dc-4a2b-8974-e20a1e770c8a
Environment
No response
Validations
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
- This issue is valid
Contributions
- I am willing to submit a PR to fix this issue
- I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
- Dominant language
- TypeScript
- Stars
- 39.3k
- Forks
- 2.2k
- Avg merge
- 9h 14m
- Merged PRs (30d)
- 16
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 RSSNext/Folo
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug platform: desktop
Difficulty 4/5 3-5 days Newbie friendliness 48/100
RSSNext/Folo#5139 · 1 comment ·
Maintainers usually reply within 1 day
-
bug need info platform: desktop
Difficulty 4/5 3-5 days Newbie friendliness 35/100
RSSNext/Folo#5055 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 50/100
RSSNext/Folo#5054 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
RSSNext/Folo#5053 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Update project links after the repository renamesPossibly taken @JonathanTSilva claimed this today. Openai-generated priority: p2 size: xs type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
JonathanTSilva/jts-website#119 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
promplate/code-review#158 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
[Docs] CONTRIBUTING points the Backend Remake milestone at a branch that does not existPossibly taken @franpts2 claimed this today. Opendocs
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 3 days
-
Split up selector calls in favourites/index?Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day