You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 21, 2021. It is now read-only.
A good explanation of why I should use the django-permission and not django-guardian also would be great, and a crazy idea, it is also if possible to use them together.
I found it very interesting implementation of role-based permissions, as you implemented in "third-impact"[1] project ( some of you seem to like Neon Genesis Evangelion 😆)
seems to me an excellent candidate to enter as an example in the documentation
Yeah, I agree with your idea I'll try when ever I got a time to do.
Writing the documentation is always most difficult things....
and a crazy idea, it is also if possible to use them together.
Theoretically you can. I have not tried so theoretically.
I found it very interesting implementation of role-based permissions, as you implemented in "third-impact"
Oh, you found that lol. Well that project is the on-going one and the new styled role-based permission is also trial strategy (it might be buggy while I'm removing is_staff and is_superuser in database level with some hackish code https://github.com/kawazrepos/third-impact/blob/is_staff_issue/src/kawaz/core/personas/models.py#L51). So I need to confirm the stability of that strategy first.
Actually this django-permission or other django plugins on my github were made for building that project. Thus the qualities of my plugins will be improved within several month by using these plugins heavily in that big project :-)
some of you seem to like Neon Genesis Evangelion 😆
More detailed documentations like below are required.
systems like django-guardian
object permission system
permission_required
decoratoruser
instance andobject
instanceautomatically
if
template taghas
andof
)if
template tag and the way to usepermission
tag in that caseI need some persons who check my English to improve the documentations lol.
The text was updated successfully, but these errors were encountered: