Feature / Idea(s): Expose lower level APIs about talkback HOT 4 CLOSED

Hi @hartzis, I'm glad that you have found talkback this useful.

I really liked your idea of exposing the request handler API.

I just released a new version 2.2.0 which includes this feature.
https://github.com/ijpiantanida/talkback#talkbackrequesthandleroptions-partialoptions-promiserequesthandler
(I think I'm reaching the limits of what one README can handle 😄 ).

I've also included an example using puppeteer
https://github.com/ijpiantanida/talkback/blob/master/examples/request-handler/start.js

from talkback.

📓 In the process of exploring and vetting the above ideas and thoughts I stumbled across something very similiar useing pollyJS.

• https://github.com/Netflix/pollyjs/blob/master/examples/jest-puppeteer/__tests__/dummy-app.test.js

from talkback.

For the middleware idea, I'm not sure if I'm understanding it correctly.
If we're talking about intercepting request coming to /api/* and returning a saved response when they exist, or continuing the middleware chain if not, then I'm not sure it's something that I'd like to implement.
I see how it can be convenient, but I don't like the idea of messing with the server's actual behavior. For now, I'm trying to keep talkback as an outside layer.

Now, if we're talking about providing a middleware just to mount Talkback without opening a new port, then that's something that can easily be implemented with the new request handler API

Feel free to open a new issue where we can discuss this further if I'm missing the point.
Thank you for these great ideas!

from talkback.

@ijpiantanida Wow, thank you, this is amazing! Even including an example with puppeteer!

The length of the readme is nothing btw, check out nock's readme, 1600 lines lol. I personally like a detailed readme. It can be nice to have all the details in one place.

I think more about the "middleware" idea, but i think a lot can be done with the new requestHandler api.

Again thank you!

from talkback.