Refactor privilege management to support hierarchical privilege keys
- Updated privilege key structure to use a 3- or 4-part dotted hierarchy (e.g., `GROUP.PARENT.MODULE`). - Modified the `RequirePrivilege` decorator to accept multiple keys, allowing for OR logic in privilege checks. - Enhanced `PrivilegesGuard` to validate against multiple privilege keys, improving access control logic. - Created migration scripts to update existing privilege keys in the database to the new format. - Updated related services, controllers, and tests to accommodate the new privilege key structure and validation logic.
This commit is contained in:
@@ -262,6 +262,24 @@ export class PrivilegesService {
|
||||
return this.privilegesRepository.checkPermission(userId, keyCode, action);
|
||||
}
|
||||
|
||||
async checkAnyPermission(
|
||||
userId: string,
|
||||
keyCodes: readonly string[],
|
||||
action: PrivilegeAction,
|
||||
): Promise<boolean> {
|
||||
if (keyCodes.length === 0) {
|
||||
return false;
|
||||
}
|
||||
if (keyCodes.length === 1) {
|
||||
return this.checkPermission(userId, keyCodes[0], action);
|
||||
}
|
||||
return this.privilegesRepository.checkAnyPermission(
|
||||
userId,
|
||||
keyCodes,
|
||||
action,
|
||||
);
|
||||
}
|
||||
|
||||
async getPermissionsMap(
|
||||
privilegeId: string,
|
||||
): Promise<Record<string, Record<PrivilegeAction, boolean>>> {
|
||||
|
||||
Reference in New Issue
Block a user