New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OKTA-295706 add usertypes #378
Conversation
updatedUserType.Description.Should().Be(updatedDescription); | ||
updatedUserType.DisplayName.Should().Be(updatedDisplayName); | ||
|
||
var retrievedForValidation = await testClient.UserTypes.GetUserTypeAsync(createdUserType.Id); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: I suggest using more descriptive names. I would rename this to retrievedUserTypeForValidation
, so we know it is a user type.
replacedUserType.DisplayName.Should().Be(replacedDisplayName); | ||
replacedUserType.Name.Should().Be(testName); | ||
|
||
var retrievedForValidation = await testClient.UserTypes.GetUserTypeAsync(createdUserType.Id); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: descriptive names. See above.
|
||
try | ||
{ | ||
HashSet<string> allUserTypeIds = new HashSet<string>(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: In this method we have vars and explicitly typed vars, let's try to use the same coding rules when it's possible for consistency. In general, this SDK is using vars, so I would stick to it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good in general. Just a few minor things.
Issue #
OKTA-295706
Code