MobileNativeFoundation / MobileNativeFoundation/Store
[Feature Request] getOrError and freshOrError
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.4k
- Forks
- 217
- Avg merge
- 18m
- Merged PRs (30d)
- 4
Description
Additionally: have you considered adding a getOrError() (and freshOrError()) that return a Result to the API? These are two functions I end up readding into all of my projects using Store, since the appropriate way to have a fetcher fail is by throwing. Which is fine if you're using .stream(), and much less fun if you forgot about that detail and called get() blindly
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 reading the Store API around get(), fresh(), and stream() to understand their existing failure behavior and return types. Determine the intended Result behavior for getOrError() and freshOrError(), then add coverage for the new API methods and their failure cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100