webmock has quite a bit of logic in their QueryMapper class https://github.com/bblimke/webmock/blob/9ff63ac7c845a75278e43236e0128e197f597462/lib/webmock/util/query_mapper.rb#L4
Right now ours is basically a dummy function that returns itself unless NULL.
Not sure I have the time or if it makes sense to port that line for line. Perhaps it makes more sense to build on something else if it exists or not, not sure if its worth it yet
I am pretty sure though that we likely do not have good behavior for more complicated request bodies
webmock has quite a bit of logic in their QueryMapper class https://github.com/bblimke/webmock/blob/9ff63ac7c845a75278e43236e0128e197f597462/lib/webmock/util/query_mapper.rb#L4
Right now ours is basically a dummy function that returns itself unless NULL.
Not sure I have the time or if it makes sense to port that line for line. Perhaps it makes more sense to build on something else if it exists or not, not sure if its worth it yet
I am pretty sure though that we likely do not have good behavior for more complicated request bodies