#16094 closed Cleanup/optimization (fixed)
Documentation for Custom permissions is ambiguous.
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Documentation | Version: | 1.3 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
The example in http://docs.djangoproject.com/en/1.3/topics/auth/#custom-permissions is not clear. A few extra permissions are defined, e.g. "can_view", but it wasn't clear to me whether this would result in an "app.can_view" or "app.can_view_task" permission. Essentially in order to figure out what would happen, I had to create a test permission and run syncdb.
Attachments (2)
Change History (11)
comment:1 by , 14 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 13 years ago
UI/UX: | unset |
---|
by , 13 years ago
Attachment: | patch.diff added |
---|
comment:5 by , 13 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
There was a missing colon in the original patch. I've corrected this attached the patch.
comment:6 by , 13 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
Thanks for pointing this out, but it'd have been more useful if the patch was based on the latest trunk :)
The missing colon is at the end of the sentence "Continuing the above example, the following checks if a user may". This might have to be backported to 1.3.X to fix r16814.
I've attached a patch that will hopefully make things clearer.