thunderbird / thunderbird/thunderbird-android
Move functionality from RecipientLoader to its own class
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
Once PR #962 is merged, move functionality from RecipientLoader to its own class(es). That way both testing and changing the method to perform the work off the main thread later will be much easier.
The fact that the loader is registering content observers make this a bit more complicated. So this should probably not done by a beginner.
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
Read RecipientLoader and PR #962 first to understand the functionality being moved and how content observers are registered. Done means the loader's work is placed in its own class or classes while preserving the existing observer behavior; verify against the current tests and behavior described around PR #962.
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
- 35/100