Make acceptance test function getUserDisplayName more robust #31755
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Phil Davis [email protected]
Description
Check if the
displayname
array entry for the user exists before accessing it.Related Issue
#31747
Motivation and Context
The code in
getUserDisplayName()
could fail with:if passed a username that it knew nothing about.
That happened in a scenario run from
user_ldap
app.Make it more robust so that it returns the passed-in username if it cannot find a displayname.
How Has This Been Tested?
Local run of:
Types of changes
Checklist: