feat(directory): Phase 3 — Reviews / MDM / Tags / Teams / DP+DC team-member#413
Open
larsgeorge-db wants to merge 1 commit into
Open
feat(directory): Phase 3 — Reviews / MDM / Tags / Teams / DP+DC team-member#413larsgeorge-db wants to merge 1 commit into
larsgeorge-db wants to merge 1 commit into
Conversation
…member Stacks on Phase 2 (#412). Five mechanical surfaces migrated onto PrincipalPicker per plan #375. No backend changes. UI changes: - data-asset-reviews/create-review-request-dialog.tsx — reviewer_email Input -> PrincipalPicker(single, user). - mdm/create-review-dialog.tsx — reviewer_email Input (RHF-managed) wrapped in a Controller bound to PrincipalPicker(single, user). - settings/tags-settings.tsx — permissionForm.group_id Input -> PrincipalPicker(single, group). Backend ACL contract unchanged. - teams/team-form-dialog.tsx — member_identifier Input -> PrincipalPicker, accepts narrows on member_type via the new principalAcceptsForMemberType helper. - data-products/team-member-form-dialog.tsx — username Input -> PrincipalPicker(single, user). Backend payload (username) unchanged. - data-contracts/team-member-form-dialog.tsx — email/username Input -> PrincipalPicker(single, user). buildContractTeamMember helper preserves the dual ``username`` + ``email`` field population the ODCS endpoint expects. Helpers (pure, fully tested): - lib/team-members.ts — principalAcceptsForMemberType for Teams type-switching, buildContractTeamMember for the DC dual-population. Tests (6 new, 705 total passing): - lib/team-members.test.ts: accepts filter narrows correctly for user/group/unknown member_type; defaults to ['user'] on null / undefined / unrecognised values. buildContractTeamMember populates both username and email with the picked id, trims whitespace on every field, and omits ``name`` entirely when blank. Per-page form-dialog mounts continue to be deferred to E2E (Radix dialogs hang in jsdom — same convention as the existing skipped role/team/project form tests). The DC dialog still preserves its basic ``@`` -> email-shape validation; PrincipalPicker can emit either an email or a plain username so the regex only fires when the value contains ``@``.
larsgeorge-db
added a commit
that referenced
this pull request
May 21, 2026
…r scope Documents what shipped under PRs #406 / #407 / #412 / #413 / #416 / #417: - Renames the integration's manager / routes / settings keys in the PRD to match the implementation (Directory layer, /api/directory/*, DIRECTORY_* settings, Settings → Directory tab). - Documents the DirectoryProvider interface and the (DirectoryProviderContext, DirectoryProviderConfig) factory signature so future provider plug-ins know what to implement. - Documents the v1 provider set, which expanded during planning from Entra-only to entra + lakebase + file. The Lakebase table schema and CSV format are included so operators have a single reference. - Preserves story content, the disambiguation rule, both picker modes, storage-compatibility guarantees, and graceful-degradation rules from the PRD body unchanged. - Re-confirms the out-of-scope list (Okta/Ping, service principals, OBO, profile photos, manager hierarchy, role/team Select replacement, CSV bulk import) which the abstraction makes cheap to revisit.
larsgeorge-db
added a commit
that referenced
this pull request
May 21, 2026
…r scope Documents what shipped under PRs #406 / #407 / #412 / #413 / #416 / #417: - Renames the integration's manager / routes / settings keys in the PRD to match the implementation (Directory layer, /api/directory/*, DIRECTORY_* settings, Settings → Directory tab). - Documents the DirectoryProvider interface and the (DirectoryProviderContext, DirectoryProviderConfig) factory signature so future provider plug-ins know what to implement. - Documents the v1 provider set, which expanded during planning from Entra-only to entra + lakebase + file. The Lakebase table schema and CSV format are included so operators have a single reference. - Preserves story content, the disambiguation rule, both picker modes, storage-compatibility guarantees, and graceful-degradation rules from the PRD body unchanged. - Re-confirms the out-of-scope list (Okta/Ping, service principals, OBO, profile photos, manager hierarchy, role/team Select replacement, CSV bulk import) which the abstraction makes cheap to revisit.
6778b9a to
58eaf6b
Compare
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.
Phase 3 of the directory-lookup-and-principal-picker plan (#375). Stacked on #412 — base is
feat/directory-phase2so the diff here is Phase-3 only. Rebases ontomainonce the rest of the stack lands.Plan: #375
Backend: #406
Phase 1 frontend: #407
Phase 2: #412
Summary
Five mechanical migrations onto
PrincipalPicker. No new backend routes; every existing endpoint accepts the same payload shape it already did.reviewer_emailreviewer_emailController)permissionForm.group_idmember_identifieracceptsflips between['user']and['group']on the row'smember_typetoggleusernameusername)usernameandemailfor ODCS backward compat)Helpers added
lib/team-members.ts:principalAcceptsForMemberType(memberType)— Teams type-switching.buildContractTeamMember({emailOrUsername, role, name})— DC dual-population helper (trims, omitsnamewhen blank, populates bothusernameandemailwith the same picked id).Test plan
yarn type-check).lib/team-members.test.ts):principalAcceptsForMemberType:'user'→['user'],'group'→['group'], defaults to['user']fornull/undefined/''/ unrecognised values.buildContractTeamMember: populates bothusernameandemailwith the picked id; trims surrounding whitespace on every field; omitsnameentirely when blank or undefined.role-form-dialog.test,team-form-dialog.test,project-form-dialog.test,tag-selector.test).Acceptance criteria from the plan (Phase 3)
member_typefromusertogroupresets the picker'sacceptsfilter without losing form state for the other row fields (per-row picker remounts; sibling rows and the row's role / domain / project fields stay intact).What's intentionally not here
Both land in Phase 4.