refactor(invitation): rename methods for consistency and enhance invitation deletion logic
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
<div>
|
||||
<div class="flex items-start gap-2 pb-10">
|
||||
<div>
|
||||
<h1>Tags</h1>
|
||||
<h1 class="pb-2">Tags</h1>
|
||||
<div>Tags help you to perform actions on multiple resources.</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -18,8 +18,8 @@
|
||||
<div class="flex items-center justify-center gap-2 mx-4 text-xs font-bold ">
|
||||
<x-modal-confirmation title="Confirm User Deletion?" buttonTitle="Delete" isErrorButton
|
||||
submitAction="delete({{ $user->id }})" :actions="[
|
||||
'The selected user will be permanently deleted from Coolify and the database.',
|
||||
'All resources (application, databases, services, configurations, servers, private keys, tags, etc.) related to this user will be deleted from Coolify and from the server (if the server is reachable).',
|
||||
'The selected user will be permanently deleted from Coolify\'s database.',
|
||||
'All resources (application, databases, services, configurations, servers, private keys, tags, etc.) related to this user\'s default team will be deleted from Coolify\'s database.',
|
||||
]"
|
||||
confirmationText="{{ $user->name }}"
|
||||
confirmationLabel="Please confirm the execution of the actions by entering the User Name below"
|
||||
|
||||
Reference in New Issue
Block a user