In 9.0, IUserApiAsync.GetUserAsync returns Task<UserGetSingleton>, where it previously returned Task<User>. This is incompatible with the return of IOktaCollectionClient<User> from IApiUserAsync.ListUsers, requiring duplication of code to handle the two different types.
This breaking change to GetUserAsync is not mentioned in the migration guide.
What is expected to happen?
IApiUserAsync.ListUsers and IApiUserAsync.GetUserAsync return compatible types
What is the actual behavior?
IApiUserAsync.ListUsers and IApiUserAsync.GetUserAsync return incompatible types
Reproduction Steps?
Update from Okta.Sdk 8.0 to Okta.Sdk 9.0 in a project that relies on GetUserAsync returning Task<Okta.Sdk.Model.User>
Describe the bug?
In 9.0,
IUserApiAsync.GetUserAsync
returnsTask<UserGetSingleton>
, where it previously returnedTask<User>
. This is incompatible with the return ofIOktaCollectionClient<User>
fromIApiUserAsync.ListUsers
, requiring duplication of code to handle the two different types.This breaking change to GetUserAsync is not mentioned in the migration guide.
What is expected to happen?
IApiUserAsync.ListUsers
andIApiUserAsync.GetUserAsync
return compatible typesWhat is the actual behavior?
IApiUserAsync.ListUsers
andIApiUserAsync.GetUserAsync
return incompatible typesReproduction Steps?
Update from Okta.Sdk 8.0 to Okta.Sdk 9.0 in a project that relies on GetUserAsync returning
Task<Okta.Sdk.Model.User>
Additional Information?
No response
.NET Version
8.0.400
SDK Version
9.0.0
OS version
No response