On Saturday, December 30, 2017 at 1:32:21 AM UTC-8, Curtis Maloney wrote: > > > So, after a discussion with a new user on #django today I decided to > make "permissions not bound to models" a first-class feature. >
I'd recommend that anyone working on such a feature take a good look at django-rules. It works on a per-app or per-project basis, is not necessarily bound to models (but can be), has a good system for detecting conflicting rules that might be set in different parts of the codebase, and provides some nice helpers for keeping statements and conditions concise. Useful both for full-view protection and for in-template fragments. I do find the distinction is makes between `make_rule` and `make_perm` somewhat arbitrary and confusing, but otherwise they've done great work with it so far. https://github.com/dfunckt/django-rules ./s -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/051b418d-349a-4ada-92ac-42f5b587fbe0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
