Fix wrong display-name property from provisioning getUser response #72
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.
☑️ Resolves
In provisioning API
getUser
andgetCurrentUser
methods returns display name with a different property name.In this PR
@nextcloud/auth/getCurrentUser
tries both properties considering the current name as "legacy".Related: nextcloud/server#36665
🚧 Tasks
'display-name'
property as a fallback for display name