fix(users): give the cancel-invitation dialog a distinct confirm label
The cancelInvitation dialog type fell through to the generic
t('userManagement.cancel'), colliding with ConfirmDialog's own dismiss
button -- two buttons both reading "Cancel", where clicking the wrong one
does the opposite of what the user intends.
Reuse the existing userManagement.cancelInvitation key: "Cancel Invitation"
vs "Cancel" (EN), "Einladung abbrechen" vs "Abbrechen" (DE). No new key.
Refs testplan REPORT.md #19 (Part 3, I.04).
This commit is contained in:
@@ -1023,7 +1023,9 @@ export const UserManagementPage: React.FC = () => {
|
|||||||
confirmDialog.type === 'deactivate' ? t('userManagement.deactivate')
|
confirmDialog.type === 'deactivate' ? t('userManagement.deactivate')
|
||||||
: confirmDialog.type === 'activate' ? t('userManagement.activate', 'Reactivate')
|
: confirmDialog.type === 'activate' ? t('userManagement.activate', 'Reactivate')
|
||||||
: confirmDialog.type === 'delete' ? t('userManagement.delete', 'Delete permanently')
|
: confirmDialog.type === 'delete' ? t('userManagement.delete', 'Delete permanently')
|
||||||
: t('userManagement.cancel')
|
// Not the generic `cancel` — that collides with ConfirmDialog's own
|
||||||
|
// dismiss button, giving the dialog two "Cancel" buttons (QA I.04).
|
||||||
|
: t('userManagement.cancelInvitation')
|
||||||
}
|
}
|
||||||
isLoading={
|
isLoading={
|
||||||
confirmDialog.type === 'deactivate' ? deactivateUserMutation.isPending
|
confirmDialog.type === 'deactivate' ? deactivateUserMutation.isPending
|
||||||
|
|||||||
Reference in New Issue
Block a user