Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Dynamic rendering of User details
See original GitHub issueDescription
The user details screen should be dynamically rendered based on the attributes defined in User Profile.
For each attribute, it should take all attribute settings into account when deciding which component to use for rendering. For instance, if an attribute uses an options validator it would only allow the user to choose the specified options.
It should also render help text if available.
It should also take into account the edit and view settings for the administrator, as well as the Required flag.
Note that for each attribute rendered on the user details screen, we should not display that attribute on the Attributes tab. However, it should still be possible to use the Attributes tab for values that are not related to User Profile.
Discussion
No response
Motivation
No response
Details
No response
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@edewit Created https://github.com/keycloak/keycloak/pull/15257. It should enable fetching the metadata associated with attributes defined in the user profile configuration.
That is correct. We haven’t done this for account ui yet. I expect that once we get some logistical things done we can get to that quickly. We can probably reuse some of the code we did for admin in the account console.