[Migration] Level System for Places and users #42
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Original https://git.mowoe.com/reverend/lostplaces-backend/issues/42 by @reverend from Thu, 24 Dec 2020 14:35:40 CET
Places and Users should have a level assigned to.
The place-level indicates how good the place is/how worthy it is of keeping it secret, where as the user-leve indicates how trustworthy a user is. Only trustworthy users should be able to see high level places.
The place level is assigned by users who are trustworthy enough. A user, wich level is to low, should not be able to assign a level to any places, not even to his own ones. Furthermore should the option to assign a level only be visbile to users who are eligible to do so.
A user can still see his own places, even if the place is assigned a level that is to high for the user.
The user level is assigned by admins.
The levels should range from 1-5,
Level 1 is default for users and indicates the lowest trustworthiness
Level 5 is default for places and indicates a high worth of protection.
Comment by @Commander1024 from Fri, 01 Oct 2021 20:26:57 CEST
Still needs frontend integration.
Comment by @reverend from Sat, 02 Oct 2021 00:06:41 CEST
The assigned level is now considered in the following scenarios:
(This doe's not let the use access any data tho, but it's more consistent)
Whenever such request is made, the user is presented with an HTTP 403 response and an according error message.
Comment by @reverend from Sat, 02 Oct 2021 00:09:23 CEST
This also takes in consideration the superuser status of the requesting user and checks if the user is the submitter
This feature is almost done, there is some workl left on the frontend side. But the PlaceDetailView-Page is about to be re designed, just looks awefull.