kellpossible / kellpossible/coster
Asynchronous Actions
- Dominant language
- Rust
- Stars
- 13
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Database actions might take a long time, same with synchronization actions. Perhaps we need a way to do asynchronous effects.
This article seems to do a fairly comprehensive comparison of the available options related to redux https://sandstorm.de/de/blog/post/async-redux-middleware-comparison.html
[redux-loop](https://github.com/redux-loop/redux-loop) appears to be the most simple solution, basically, basically just an async call from the reducer which dispatches an action back on the store upon completion.
_Originally posted by @kellpossible in https://github.com/kellpossible/coster/issues/12#issuecomment-637979697_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the linked comparison of Redux middleware options and the redux-loop project. Then trace the database and synchronization actions to determine where asynchronous effects would fit and how completion should dispatch back to the store. Done means the project has an agreed, working approach for long-running actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redux, rust
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100