Overlay lifecycle changes
Open
enhancement
- Dominant language
- Kotlin
- Stars
- 164
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
When pushing an overlay there is no way for the previous rib to understand that an overlay is present on top of it.
Make it possible for the previous rib to receive that information. E.g Resume/Pause state.
Why is this a problem?
E.g: Track viewScreen
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the overlay-push lifecycle and the previous RIB's Resume/Pause state handling, then trace the Track viewScreen use case. Done means the previous RIB can receive reliable information that an overlay is present, with the expected lifecycle state defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100