wordpress-mobile / wordpress-mobile/WordPress-Android
[Reader] Remove EventBus from the data layer
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
It would greatly improve code maintainability and testability (and hence how fast we implement changes) if we removed EventBus from the context of Reader's data layer, specifically from post list requests. Since the Reader's APIs are implemented directly on WordPress-Android (instead of FluxC) it might be easier to remove EventBus here than in other places.
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 the Reader data layer's post list request flow and identifying where EventBus is used. Review how the Reader APIs are implemented directly in WordPress-Android, then determine the replacement flow and verify that post list requests retain their current behavior without EventBus.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100