[`LookerSDK.client. merge_content_type_if_body`](https://github.com/looker/looker-sdk-ruby/blob/29ffd749985d092c98db3f7664dbecbbd9af5c92/lib/looker-sdk/client.rb#L481) fails to delete `options[:headers]` (as for instance [`LookerSDK.client.parse_query_and_convenience_headers`](https://github.com/looker/looker-sdk-ruby/blob/29ffd749985d092c98db3f7664dbecbbd9af5c92/lib/looker-sdk/client.rb#L493) correctly does) so the caller must supply `content_type` in order for the call to work. E.g I'd expect the following to pass both `"my-header"` and `"content_type"` headers to the server: ```ruby sdk.create_some_resource( {resource_name: "foo", an_attr: "bar"}, {headers: {"my-header" => "something"}}, ) ``` instead it only passes `"my-header"` and so the caller must do the following to get it to work: ```ruby sdk.create_some_resource( {resource_name: "foo", an_attr: "bar"}, {headers: {content_type: "application/json", "my-header" => "something"}}, ) ```
LookerSDK.client. merge_content_type_if_bodyfails to deleteoptions[:headers](as for instanceLookerSDK.client.parse_query_and_convenience_headerscorrectly does) so the caller must supplycontent_typein order for the call to work.E.g I'd expect the following to pass both
"my-header"and"content_type"headers to the server:instead it only passes
"my-header"and so the caller must do the following to get it to work: