You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We believe that there is an error with the return type of the Get Items Batch call.
Currently, both the Microsoft Learn documentation and the azure-devops-rust-api expects the return type for the call to return a Vec<String> (for rust) or an array[] (for C#).
We believe that this is an error, because when invoking the .into_body() method implemented for the Get Items Batch call, we get the "failed to deserialize" response with the additional context that "invalid type: map, expected a sequence at line 1 column 0".
Moreover, similar API calls like Get Item have a more sophisticated return type. In this case, Get Item expects a GitItem object.
Currently we are looking to custom deserialize as a workaround but do let us know if this this something we could update in the patching layer for the Rust SDK. Happy to answer any questions as well! :)
The text was updated successfully, but these errors were encountered:
We believe that there is an error with the return type of the Get Items Batch call.
Currently, both the Microsoft Learn documentation and the azure-devops-rust-api expects the return type for the call to return a
Vec<String>
(for rust) or anarray[]
(for C#).We believe that this is an error, because when invoking the
.into_body()
method implemented for the Get Items Batch call, we get the "failed to deserialize" response with the additional context that "invalid type: map, expected a sequence at line 1 column 0".Moreover, similar API calls like Get Item have a more sophisticated return type. In this case, Get Item expects a GitItem object.
Currently we are looking to custom deserialize as a workaround but do let us know if this this something we could update in the patching layer for the Rust SDK. Happy to answer any questions as well! :)
The text was updated successfully, but these errors were encountered: