Bartosz Blimke
Bartosz Blimke
@weppos thank you for reporting the issue. Could you please let me know what is the issue you are experiencing as a side effect of that behaviour of the request...
@aeden does it help if you set `WebMock::Config.instance.query_values_notation = :flat_array`?
@aeden thanks. Does it match if you change the query params to "street"=>["1234 SW 1st Street", "Apt 3"]?
@surkova could you please provide an example? Is there a problem with matching query or headers in your case?
@surkova thank you for clarifying. have you tried setting `WebMock::Config.instance.query_values_notation = :flat_array`?
@surkova I agree it's confusing. It should be at least mentioned in README.
@surkova it's not possible. I think it will also be a pain to know when to use flat array and when not to, therefore it would be better to either...
@surkova > the library should always assume there can be duplicate keys in the query I agree. The reason is the representation of query parameters as a hash, same limitation...
Thank you @ssankim The change looks good, but the tests would have to be improved as I mentioned in the issue: "The change will have to be applied and tested...
@ulyssesrex thank you for pointing that. SOAPAction is indeed a culprit. I guess this can be changed in WebMock but with major version change in WebMock as I it would...