Rethink permission handling for subject/courses #18

Closed
opened 2024-05-21 14:08:53 +02:00 by yuha · 4 comments
Member

For now, the get_queryset method of SubjectType filters for permission ownership of the default django view permission – which has to be manually assigned. This is handled differently for CourseType where there is only a check whether the user has a person. Both ways of dealing with that don't seem particularly good...

For now, the `get_queryset` method of `SubjectType` filters for permission ownership of the default django view permission – which has to be manually assigned. This is handled differently for `CourseType` where there is only a check whether the user has a person. Both ways of dealing with that don't seem particularly good...
Author
Member

assigned to @yuha

assigned to @yuha
Author
Member

created branch 18-rethink-permission-handling-for-subject-courses to address this issue

created branch [`18-rethink-permission-handling-for-subject-courses`](/AlekSIS/onboarding/AlekSIS-App-Cursus/-/compare/master...18-rethink-permission-handling-for-subject-courses) to address this issue
Author
Member

mentioned in merge request !94

mentioned in merge request !94
Owner

mentioned in commit 18fc4ad9d6

mentioned in commit 18fc4ad9d64d90b83b51f1249e0213d1ad313a68
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
aleksis/AlekSIS-App-Cursus#18
No description provided.