shahondin1624/Mitgliederverwaltung
Public Access
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 16 Wiki Activity

feat: add PermissionService with access level checks (Closes #36) #82

Merged
shahondin1624 merged 1 commits from feature/issue-36-permissionservice-implementation into main 2026-04-07 12:33:11 +02:00
Conversation 0 Commits 1 Files Changed 3
+338
shahondin1624 commented 2026-04-07 12:33:07 +02:00
Owner
Copy Link
Copy Source

Summary

  • Creates Permission entity with JSON-decoded allowed Stufen helper
  • Creates PermissionMapper with findByUserId and findAll
  • Creates PermissionService with all required access checks:
    • canAccess, canRead, canWrite (with Stufe-level checking), canWriteStufe
    • isAdmin, canSeeBanking, getVisibleStufen
    • Admin methods: setPermission (create-or-update), removePermission

Access Level Hierarchy

none < read < stufe < full < admin

Closes #36

## Summary - Creates `Permission` entity with JSON-decoded allowed Stufen helper - Creates `PermissionMapper` with findByUserId and findAll - Creates `PermissionService` with all required access checks: - `canAccess`, `canRead`, `canWrite` (with Stufe-level checking), `canWriteStufe` - `isAdmin`, `canSeeBanking`, `getVisibleStufen` - Admin methods: `setPermission` (create-or-update), `removePermission` ## Access Level Hierarchy none < read < stufe < full < admin Closes #36
shahondin1624 added 1 commit 2026-04-07 12:33:07 +02:00
feat: add PermissionService with access level checks (Closes #36) efe0c1c36f 
Implement Permission entity, mapper, and PermissionService with:
- canAccess, canRead, canWrite, canWriteStufe, isAdmin, canSeeBanking
- Stufenzugriff support (write only members in allowed Stufen)
- Admin methods: getAllPermissions, setPermission, removePermission
- Banking visibility as separate flag

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
shahondin1624 merged commit 3b3a634864 into main 2026-04-07 12:33:11 +02:00
shahondin1624 deleted branch feature/issue-36-permissionservice-implementation 2026-04-07 12:33:12 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
backend
Backend / PHP work
 bug
Bug report
 database
Database migrations and schema
 documentation
Documentation
 enhancement
Enhancement or improvement
 epic
Epic / feature-group issues
 frontend
Frontend / Vue.js work
 integration
Nextcloud integrations (Calendar, Contacts, Files)
 priority:high
High priority
 priority:low
Low priority
 priority:medium
Medium priority
 security
Security-related work
 testing
Tests and test infrastructure
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shahondin1624
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shahondin1624/Mitgliederverwaltung#82
Delete Branch "feature/issue-36-permissionservice-implementation"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?