backend: Rename recording permission middleware for clarity and consistency

backend/src/middlewares/recording.middleware.ts

@@ -48,7 +48,7 @@ export const withRecordingEnabled = async (req: Request, res: Response, next: Ne
 	}
 };
 
-export const withCorrectPermissions = async (req: Request, res: Response, next: NextFunction) => {
+export const withCanRecordPermission = async (req: Request, res: Response, next: NextFunction) => {
 	const roomId = extractRoomIdFromRequest(req);
 	const payload = req.session?.tokenClaims;
 

backend/src/routes/recording.routes.ts

@@ -7,7 +7,7 @@ import {
 	participantTokenValidator,
 	tokenAndRoleValidator,
 	withRecordingEnabled,
-	withCorrectPermissions,
+	withCanRecordPermission,
 	withValidRecordingFiltersRequest,
 	withValidRecordingBulkDeleteRequest,
 	withValidRecordingId,
@@ -62,7 +62,7 @@ internalRecordingRouter.post(
 	withValidStartRecordingRequest,
 	withRecordingEnabled,
 	withAuth(participantTokenValidator),
-	withCorrectPermissions,
+	withCanRecordPermission,
 	recordingCtrl.startRecording
 );
 
@@ -71,6 +71,6 @@ internalRecordingRouter.post(
 	withValidRecordingId,
 	withRecordingEnabled,
 	withAuth(participantTokenValidator),
-	withCorrectPermissions,
+	withCanRecordPermission,
 	recordingCtrl.stopRecording
 );