I was unaware of this. I kinda wish we didn't have both a body and json_body input. Maybe just because context.fetch has them as separate properties.
If left how it currently is, could it cause the POST to fail due to putting the body on the wrong property?
To answer your actual question, I'm fine for it to be as is - for the sake achieving the goal of putting this integration in the codebase. But if it's causing a potential bug, then I think we should fix it shortly afterwards. Let me know if I'm misunderstanding what's going on with it 🙂
Originally posted by @QuantumNightmare in #177 (comment)
Originally posted by @QuantumNightmare in #177 (comment)