Repository navigation
feat: configurable user profile information - #5
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Profiles can now show selected custom user fields and values reached through single-record relationships. For example, an administrator can show a department name and its manager in both the account profile and the user editor without copying data or hardcoding collection names.
A superuser configures up to 12 rows in Users → Profile display, including their labels, order and explicit visibility to the profile owner. Users with
users/readcan read configured rows in user cards; owners receive only rows enabled for them. This grants access only to the selected values, not to the underlying directories or editing. Sensitive fields, built-in user columns and unsupported relationship targets are excluded. Changed or replaced source bindings stop disclosing their values until reconfigured.The change includes an additive configuration migration, typed HTTP contracts and OpenAPI, Russian/English UI copy, and authorization regression coverage. Existing installations start with an empty configuration. No demo data is included.
Validation: 493 Core tests passed (3 optional checks skipped), all 143 UI tests passed, and the focused profile/relationship suite passed 16 tests. Typecheck, lint, formatting, application/documentation builds and package archives installed in a clean consumer passed. Local browser checks covered configuration saving, account and user-card display, and a 390 px viewport. GitHub CI passed the complete checks, split-container smoke test and Helm chart/routing validation.