Why?

A user reported that specifying null as a value in an input param hash was not working; the key/null value was being stripped from the params as the request was being built. This was likely the correct behavior for v1 APIs but in v2 null is a valid parameter value for many fields.

What?

• adds semantics parameter to Util.objects_to_ids and changes Hash case to preserve nil values when semantics is v2
• updates calls to Util.objects_to_ids to pass api mode as semantics
• adds tests for objects_to_ids

See Also

go/j/RUN_DEVSDK-2126

Changelog

• Nil input params are now preserved when calling V2 APIs. Add additional tests for nil when calling V2 services you do not accidentally include an unintentional nil value. V1 API calls are not affected (nil values are stripped from params hashes in V1).