Create staff member tRPC procedures

[L-Mario564]

For each procedure:

• Apply rate limit middleware.

(All inputs listed are required/must be defined unless stated with ? appended at the end of the variable name).

Search users

Get a list of users via an inputted string.

Input: query, tournamentId, admin?.

Conditions

• Session user must be a staff member with the permissions host, manage_tournament.
• Tournament is not deleted.
• Tournament hasn't concluded.
• No banned users.
• The query string must be either equal to a user's ID, osu! user ID, Discord user ID or is like the osu! username (use pg_trgm for that last one).
• If admin is true then only return admin users.
• Limit of 20.
• Order ascendingly by osu! username.

Return

• User.id
• User.osuUserId (or OsuUser.osuUserId)
• OsuUser.username
• Whether or not (boolean) the user is already a staff member in that tournament.

Send join staff invite

Insert a record into the Invite table and insert records into InviteWithRole table accordingly.

Input: toUserId, tournamentId, staffRoleIds. Notes

• reason = join_staff.
• byUserId = ID of the session user.

Conditions

• Session user must be a staff member with the permissions host, manage_tournament.
• Tournament is not deleted.
• Tournament hasn't concluded.
• The invited user isn't banned.
• staffRoleIds must have at least one element.
• Each staff role in staffRoleIds must be a role within that tournament.
• Host and debugger roles can't be assigned via this procedure.
• Only the host can assign a role with manage_tournament permissions.

Send join staff as debugger invite

Insert a record into the Invite table and insert records into InviteWithRole table so the user can be assigned the debugger role.

Input: toUserId, tournamentId. Notes

• reason = join_staff.
• byUserId = ID of the session user.

Conditions

• Session user must be a staff member with the permissions host.
• Tournament is not deleted.
• Tournament hasn't concluded.
• The invited user isn't banned.
• The invited user is an admin.

Accept join staff invite

Insert a record into the StaffMember and StaffMemberRole tables and set Invite.status to accepted.

Input: inviteIds. Notes

• Get the tournament via Invite.tournamentId.
• Get the staff role IDs via InviteWithRole.staffRoleId.
• StaffMember.userId should be the same as Invite.toUserId.

Conditions

• Invite.status should be pending.
• Invite.toUserId should be the same as the session user's ID.
• If a StaffMember record with the same user ID and tournament ID already exists and it's soft deleted (deletedAt is defined and past the current date) then instead of inserting, update that record by setting deletedAt to null and joinedStaffAt to now().

Accept staff registration response

Insert a record into the StaffMember and StaffMemberRole.

Input: formResponseId, staffRoleIds. Notes

• StaffMember.userId = FormResponse.submittedByUserId

Conditions

• Session user must be a staff member with the permissions host, manage_tournament.
• Tournament is not deleted.
• Tournament hasn't concluded.
• The user who submitted the response isn't banned.
• staffRoleIds must have at least one element.
• Each staff role in staffRoleIds must be a role within that tournament.
• Host and debugger roles can't be assigned via this procedure.
• Only the host can assign a role with manage_tournament permissions.
• If a StaffMember record with the same user ID and tournament ID already exists and it's soft deleted (deletedAt is defined and past the current date) then instead of inserting, update that record by setting deletedAt to null and joinedStaffAt to now().

Update staff member roles

Insert and delete records of the StaffMemberRole tables accordingly.

Input: staffMemberId, staffRoleIds.

Conditions

• Session user must be a staff member with the permissions host, manage_tournament.
• Session user can't assign themselves any roles.
• Staff members with manage_tournament permission can't remove another staff member's roles that has that permission.
• Roles with manage_tournament permission can only be assigned and removed by the host.
• Tournament is not deleted.
• Tournament hasn't concluded.
• Staff member is not deleted.
• staffRoleIds must have at least one element.
• Each staff role in staffRoleIds must be a role within that tournament.
• Host and debugger roles can't be assigned or removed via this procedure.
• Any staff members with the debugger role can't be assigned any other role.

Pseudo-code example

current roles: [6, 7, 8]
input:         [7, 8, 9, 10]
=
remove:        [6]
add:           [9, 10]

Delete staff member

Set StaffMember.deletedAt to now() and unlink any roles assigned to this staff member.

Input: staffMemberId.

Conditions

• Session user must be a staff member with the permissions host, manage_tournament.
• Staff members with roles with manage_tournament permission can't delete other staff members with that same permission.
• Tournament is not deleted.
• Tournament hasn't concluded.
• The host can't be deleted.
• Session user can't delete themselves.

Leave staff team

Set StaffMember.deletedAt to now() and unlink any roles assigned to this staff member, said staff member being the current session user.

Conditions

• The host can't leave.
• Tournament is not deleted.
• Tournament hasn't concluded.

[L-Mario564]

To anyone who tackles this issue, please let me know if everything makes sense and also let me know if there are any other conditions to consider, as I've written plenty and could have made mistakes or forget certain interactions/scenarios.

[ArtemOsuskyi]

@L-Mario564 it would make more sense to accept one inviteId at a time instead of multiple for Accept join staff invite procedure

[ArtemOsuskyi]

@L-Mario564 why do we need staffRoleIds in input for Accept staff registration response? It'd be more logical for them to be already defined in form response at this point. Nvm, it makes sense if user applies for preferable roles and host decides to assign him roles as he sees fit

[L-Mario564]

@L-Mario564 it would make more sense to accept one inviteId at a time instead of multiple for Accept join staff invite procedure

That's a typo on my part, sorry. It's just one ID.

Nvm, it makes sense if user applies for preferable roles and host decides to assign him roles as he sees fit

Correct.