rib in a fragment
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 7.9k
- Forks
- 914
- PR merge metrics
- No merged PRs in 30d
Description
i have a rib that needs to be isolated inside a fragment. Has anyone tried this, what could be the problem? At first glance, it seems that I just have to pass the implementation of parentInterface to the builder and the rib will be able to live on its own. But there are doubts
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 tracing how the RIB builder uses parentInterface and how a RIB is hosted inside an Android fragment. Determine whether passing the parentInterface is sufficient for an isolated RIB, and document the required integration or the missing support; no specific files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100