-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Talkback could set a way to enforce req and res as humanReadable at options #56
Comments
Hi @skywalkerluc, is your response payload returning a Content-Type header? Could you paste one of the created tapes? |
We're sending 'content-type': 'application/json', here's a close example to how it's been mounted:
Hoping this to be clear enough, I can provide some other example or how our mock-server is set up. |
The server seems to be responding with the right headers that would allow talkback to uncompress and show the body in plain text ( What version of talkback are you using? |
So, we're using "talkback": "1.11.1", I know it's kinda old. Maybe updating it to the latest could help somehow? |
Ah, I see! Yes, 1.11.1 didn't have support for compressed responses yet. Unless you are using node <=10, you should be able to jump to the latest version without major issues. Keep in mind that tapes that were already stored will not get updated.
and manually making the base64 body a JSON object (not a string). This sounds like a good future feature, where talkback automatically improves the stored tapes. But I will need to think a little bit more about it. I will close the issue, but let me know if you are still having problems making it work. |
My case: everytime I run as record-mode, I'm seeing res body as base64. I believe you should be able to enforce req and res as humanReadable at options, instead of changing stuff through decorators for meta data.
The text was updated successfully, but these errors were encountered: