Joe Gomain Hoyes
Joe Gomain Hoyes
Yes, I've come across a few more inconsistency cases and this library is not to blame. It may be worth documenting the mere fact that returned data is a passthrough...
This hack works ```ts const stream = await (firstVersion).getStream().then(res => res.body); ``` Is this reliable?
Having similar issue here. I notice that when an ajax request completes very quickly I get this timeout. As if the monitoring of network being idle begins after the network...
I suggest a new constructor `withInitialState` something like this: ```ts const withIntiailState = (main, initialState: T, name) => { const sandwiched = (sources) => { const mainSinks = main(sources) return...
> Fix stream types to allow describing the first emission type, versus the subsequent emission types, then make the state sink require a type for a Stream where the first...
> Setting an initial state is an app logic realm, should be done inside Main. Main *having* state could also be regarded as app logic. Consider... ```ts const main =...
@staltz Thanks for explaining. Let me get my head around the *Cycle.js architecture*.
I believe the specifications says that, upon abort, the _reason_ (when given) would be thrown instead of the default `AbortError`. For me this is very invasive. It prevents detecting that...
Node's implementation of `fetch` does throw the given `reason`, validating that it is an object otherwise a `TypeError` is thrown.
You may want to look into [node-soap Client](https://github.com/vpulim/node-soap#client-events). The client returned by this library is essentially that.