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
Some methods have two generic parameters, e.g. T, U. This allows specifying a different document for the body and the response. However the types used for the body and the response are inconsistent across the APIs.
Example:
In DocumentApiClient, method PatchDocumentAsync<T, U> uses T for the body and U for the response.
In GraphApiClient, method PatchVertexAsync<T, U> uses T for the body and U for the response. But method PatchEdgeAsync<T, U> uses U for the body and T for the response.
We should check all methods and make sure T is used for the body and U for the response.
The text was updated successfully, but these errors were encountered:
DiscoPYF
changed the title
Type inconsistencies across APIs for methods with two generic types
Type inconsistencies for methods with two generic types
Jul 11, 2020
Some methods have two generic parameters, e.g.
T, U
. This allows specifying a different document for the body and the response. However the types used for the body and the response are inconsistent across the APIs.Example:
In
DocumentApiClient
, methodPatchDocumentAsync<T, U>
usesT
for the body andU
for the response.In
GraphApiClient
, methodPatchVertexAsync<T, U>
usesT
for the body andU
for the response. But methodPatchEdgeAsync<T, U>
usesU
for the body andT
for the response.We should check all methods and make sure
T
is used for the body andU
for the response.The text was updated successfully, but these errors were encountered: