[Android] Decouple base classes from Reactive APIs
Open
Nobody has claimed this yet.
Android
- Dominant language
- Kotlin
- Stars
- 7.9k
- Forks
- 914
- PR merge metrics
- No merged PRs in 30d
Description
If we can decouple the base classes from Rx2, then we can have extension artifacts that allow Rx2, Rx3, and Coroutines for compatibility with a variety of project types.
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
The issue names no files, tests, or entry points. Start by locating the Android base classes and their Rx2 dependencies, then determine the extension-artifact boundaries needed for Rx2, Rx3, and Coroutines. Done means the base classes no longer depend on Rx2 while compatibility artifacts support all three APIs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100