Alex Liu

@dotnetCarpenter `handleError: false` gets us partially there, but the error object isn't being passed on. I see res.statusCode being set, so we could infer an error from a non-200 statusCode...

Also, just to clarify - the _success_ scenarios also need to invoke `next()`, and that would have to be done via a new option, something like `alwaysNext: true`. That's not...

If you don't mind, I can take an initial stab at a pull request in the coming weeks. I see two parts to this: 1) Add a new option, something...

Hey, sorry, been swamped with stuff recently and this got pushed on to my backlog. I have a WIP branch I'll share in the coming weeks when I have some...

@jeevank I started the work but was unable to work through a bunch of failing tests in the time frame I had - unfortunately, never got a chance to pick...

@dotnetCarpenter I had the work sitting on a local branch on my old machine, but the HDD died over the winter break. :( I recall there wasn't a whole lot...

This is clever! I think this might accidentally convert `{"0":"zero", "1":"one"}` into an array though. With the way JSONStream works I'm not sure if there's a way to know without...

Hey @MichaelHirn - sorry this notification went into a black hole. Some minor comments but otherwise should be good to go! If you like, I can also carry this over...

Hi @Mazorati, it seems the `into-stream` module is now using async functions which isn't supported in Node6. Try Node8+?

Update: I captured the raw records being emitted by the transform stream on the `data` event, and saved those record objects. You can then feed those records into a new...