This would be a breaking change (and push us to v11), but would uniformly fix issues like the one reported today of the unwieldiness of certain search operations.
Organizations.Search() currently has the problem that a Query must be given or it fails to be parsed properly. For example, this is totally valid in cURL:
We had already special-cased Users.Search, but it doesn't address the underlying issue: there are a number of types that should be pointers that instead get sent as "zero structs" and then misinterpreted by the API.
This would be a breaking change (and push us to v11), but would uniformly fix issues like the one reported today of the unwieldiness of certain search operations.
Organizations.Search()
currently has the problem that a Query must be given or it fails to be parsed properly. For example, this is totally valid in cURL:but this fails in the Go SDK:
We had already special-cased
Users.Search
, but it doesn't address the underlying issue: there are a number of types that should be pointers that instead get sent as "zero structs" and then misinterpreted by the API.Testing
On v11, the code above succeeds: