Refactor core action to return a parser instance based on the response body

> So a change that allows conduit to own it's entire API while also isolating itself from changes to underlying libraries would be a bad thing because it could enable a driver that would "abuse" the logging capabilities of a gem that includes it as a dependency. I see.

No, a change to allow conduit to own it's API is fine... However, explicitly bypassing conduit to use it's internals is just a bad practice, and could result in unexpected results. As I said, f you have external use cases for something, you make it into a library (or in this case a gem).

BeQuick will ultimately do what they want with this gem. However, as the original author and a maintainer I would have to say :-1: to the idea of allowing accessing internals this way. It's a hacked solution that could easily be solved in a much more elegant, and full featured way.