Erki Esken

That sounds good, that there would be a default of `{provisioner: vagrant}` and any custom ones (including custom `provisioner`) would be merged into it.

I just had a need for types for `common-errors`, resorted to defining our own override types for the API surface we needed right now (some Error types and helper/generateClass stuff)....

> Such syntax would be much useful for me because there is always a risk to forget to call done(). I've found automatic linting (with eslint-loader in webpack, or as...

Yeah the processOptions way doesn't allow for multiple dispatch calls. One way to get async/await style, multiple dispatch and only do one `done` call is to use Bluebird.finally like so:...

How I did it is wrap all external REST API fetch calls in an RestApi class singleton, that is then passed as dependency to logics. So in typical logic I...

> What is in your code new Rx.Subject(); ? That's just an observable stream from [RxJS project](http://reactivex.io/rxjs/manual/tutorial.html#creating-observables). RxJS is also what redux-logic is built upon internally. To get the minimum...

Hey @jeffbski, I'm in the same team with @riston and @askot. For now we had to fork this library to fix our issues for good. Your above workaround only alleviates...

Just so Jeff has more examples of use-cases this is how I've handled chaining and waiting for other logics to finish. This example is extracted from an e-commerce app that...

> but in my redux-logic is where I integrate things: listen for actions, perform side effects, route changes, and dispatching actions. Same here. I'm fine with logic being aware of...

I would solve it with some RxJS, like so: ```js import { Subject } from "rxjs/Subject"; import "rxjs/add/operator/finally"; export const dataFetchLogic = createLogic({ type: FETCH_PAGINATED, process({ action, axios }, dispatch,...