Skip to content

feat(ui): show DN column in container-scope view#48

Merged
fdaugan merged 1 commit into
feature/vuejsfrom
norman/feat-container-scope-show-dn
May 29, 2026
Merged

feat(ui): show DN column in container-scope view#48
fdaugan merged 1 commit into
feature/vuejsfrom
norman/feat-container-scope-show-dn

Conversation

@Terracosmos
Copy link
Copy Markdown
Collaborator

Context

Issue #44 lists four fields the original AngularJS view exposed: name, type, dn, locked. In the current Vue view, name is already a column, locked is rendered as a lock icon in the Status column, and type is implicit through the Groups/Companies tabs. The remaining gap is the LDAP DN.

Fix

  • Adds a new sortable column dn between Name and Status in the container-scope datatable.
  • Adds a read-only DN text field in the edit dialog, shown only when editing an existing scope (the DN is auto-generated by the backend on creation).
  • Adds the demo DN values for consistency in demo mode.
  • New i18n key containerScope.dn (Chemin LDAP / LDAP path), contributed by the plugin and merged into the host i18n store at install.

The save payload is intentionally unchanged: the DN stays a backend concern.

Test plan

  • npm run build : OK
  • npx vitest run : OK
  • Smoke test on Identité → Portées de conteneurs: DN column visible on both tabs, DN read-only in the edit dialog of an existing scope.

Closes #44

Exposes the LDAP DN field of container scopes in the datatable (new
sortable column between Name and Status) and in the edit dialog as a
read-only text field shown only when editing an existing scope. The DN
is auto-generated by the backend, so it stays excluded from the save
payload.

Type is intentionally not added as a column because the Groups and
Companies tabs already make the type implicit on this view.
@sonarqubecloud
Copy link
Copy Markdown

@sonarqubecloud
Copy link
Copy Markdown

@Terracosmos Terracosmos requested a review from fdaugan May 29, 2026 10:34
@fdaugan fdaugan merged commit dab348c into feature/vuejs May 29, 2026
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants