Displaying 1 to 17 from 17 results

redux-logic - Redux middleware for organizing all your business logic


Use the type of code you and your team are comfortable and experienced with. Testing your logic is straight forward and simple. redux-logic-test provides additional utilities to make testing a breeze.

workflow-core - Lightweight workflow engine for .NET Standard


Workflow Core is a light weight workflow engine targeting .NET Standard. Think: long running processes with multiple tasks that need to track state. It supports pluggable persistence and concurrency providers to allow for multi-node clusters. See Tutorial here.

redux-machine - A tiny library (12 lines) for creating state machines in Redux apps


If you are using Immutable JS in your stores, see redux-machine-immutable. redux-machine internally uses Object.assign, which is an ES2015 feature. If you need to support older browsers, you can use a polyfill such as core-js.




redux-saga-rxjs - RxJS implementation of Saga pattern for redux


Redux gives us great power but with great power comes great responsibility. It's possible to build amazing, extensible, robust and scalable architecture, yet it's not as easy as it looks, because there are some unknowns which hasn't been fully solved and proven e.g. Local component State / Side effects / Long running transactions etc. One common problem that probably every developer will sooner or later have to face is communication with an API. Reading through the Redux docs will guide you to use thunk-middleware. Thunk middleware allows you to dispatch function instead of object, this is cool because the function gets called providing dispatch and getState as arguments, therefore it allows you to call the API inside the function and dispatch an action holding payload when API response arrives - this is an asynchronous operation.

node-cqrs-saga - Node-cqrs-saga is a node


Node-cqrs-saga is a node.js module that helps to implement the sagas in cqrs. It can be very useful as domain component if you work with (d)ddd, cqrs, eventdenormalizer, host, etc. The values describes the path to that property in the event message.

redux-typed-saga - A type-safe alternative to redux-saga


Redux-typed-saga is an alternative, well-typed take on the awesome redux-saga. The inspiration for typing side effects came from Redux Ship. However, Redux Ship has a totally different paradigm, and I don't want to buy into that completely.


banica - Handle async processes like a boss


Handle async processes like a boss. Implementation of the command pattern using generators. Or in other words a redux-saga but without the Redux bit. yarn add banica or npm install banica -S. The library is available also as a single JavaScript file here.

go-saga - Implements saga-pattern in Go, another way to distribute transaction.


[![GoDoc](https://godoc.org/github.com/lysu/go-saga?status.svg)](https://godoc.org/github.com/lysu/go-saga) [![Build Status](https://travis-ci.org/lysu/go-saga.svg?branch=master)](https://travis-ci.org/lysu/go-saga)

redux-saga-test - Helper for testing redux-saga


A little helper to test [redux-saga][rs]. The saga under test.

redux-saga-sc - Provides sagas to easily dispatch redux actions over SocketCluster websockets


This package provides ready to use sagas to connect SocketCluster clients. It can be used to let your server dispatch redux actions on the client and vice verca. Or to sync a shared redux state across multiple nodes or clients. You'll notice that this guide does not use the terms "server" and "client". Why? You could use this server to server, client to client, it doesn't matter. Instead you have a "sender" and a "receiver". The "sender" can emit something, the "receiver" listens for the emit and may decide to emit something back in response. The "sender" can also request something from the "receiver" requiring a response of either successType or failureType.

redux-saga-testing - A no-brainer way of testing your Sagas


Testing Sagas is difficult, and the aim of this little utility is to make testing them as close as possible to testing regular code. It should work with your favourite testing framework, although in this README the examples are using Jest.

redux-form-saga - Connecting Redux Form and Redux Saga through a saga.


Connecting Redux Form and Redux Saga through a saga. If you are using both Redux Saga and Redux Form so you need a way to handle your form submission/validation inside your sagas. redux-form-saga provides a way to handle your form inside your saga as easy as it can be.

purescript-redux-saga - Manageable I/O for Purescript apps - http://slides


Redux-saga inspired library for dealing with I/O in Purescript apps. The idea is to completely isolate all I/O from pure code, meaning that neither the reducer, nor the components, nor the action creators do any kind of I/O leaving the application mostly pure and placing all I/O into a single location. To do so, purescript-redux-saga creates a virtual thread of execution whose inputs are either actions produced by the UI or attached Sagas, or values received through "channels".

vuex-saga - Better Vuex Action To Simplify Your Async Flow Process And Code Testing


Better Vuex Action To Simplify Your Async Flow Process And Code Testing. It's inspired by redux-saga but it works differently. Vuex Saga just simplify the action for async and testing while redux-saga is being advance async flow control which can make some watchers. You can import vuex-saga.js to your vue component file like this and process it with your preprocessor.