[Question] Handle when a child becomes the parent of it's parent
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 7.9k
- Forks
- 914
- PR merge metrics
- No merged PRs in 30d
Description
I want to ask for input in a navigation logic I'm facing. I show a list of products as a RIB (it has networking, filtering and so on), from that I can open the details of a product which is another RIB (since there is logic to mark as favorite and networking) and from that details view I can see sellers that sell the same thing (sellers are also a RIB) and finally from the sellers details I can see a list of all the products so it basically becomes and infinite loop of:
ProductDetails -> SellerDetails -> ProductDetails -> ...
My question is if this is the right way to handle things or there is a better logic than just keep adding ribs on top of each other. I made a project that shows this loop https://github.com/Edhoru/RIBsChildBecomesParent
Thanks
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 linked RIBsChildBecomesParent reproduction and its ProductDetails, SellerDetails, and product-list navigation flow. No source files or tests are named in the issue; done would require an agreed approach for the repeated ProductDetails–SellerDetails cycle rather than simply stacking more RIBs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100