Fix UserProfile component in AsgardeoV2 platform #354
Merged
+114
−31
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.
Purpose
This pull request addresses issues with the
UserProfilecomponent for the AsgardeoV2 platform, enhancing its compatibility and improving the user interface and flexibility. The main changes include a UI redesign for the profile display, support for custom display name attributes, and adjustments to ensure correct behavior when SCIM2 schemas are unavailable.UserProfile component improvements:
profileSummarysection with avatar, display name, and email at the top, followed by user attributes in labeled rows with dividers for better readability. [1] [2]profileSummary,sectionRow,sectionLabel, andsectionValue. [1] [2] [3]displayNameAttributesprop, allowing consumers to specify which user attributes to prioritize for the display name. [1] [2] [3]emailkey in addition toemails.Platform-specific fixes for AsgardeoV2:
Other enhancements:
Related Issues
Related PRs
Checklist
Security checks