Add class name interpolation in Meta.permissions codenames

[faldridge]

I've got a patch for a slight behavior modification that I needed and that might be useful for others, and I wanted to collect some thoughts on it before writing up the regression tests and documentation changes.

Twice now, I've come across a situation where the default Django behavior for inheriting permissions is inappropriate for my security model.

Here's the situation: I have a permission on an abstract base model class that I want all child classes to inherit, and I want to then append specific permission(s) to one or more of the children.

Example:

class MyAppBaseModel(models.Model):
    class Meta:
        abstract = True
        permissions = (("view_%(class)s", "Can view %(class)s"),)

class ChildModel(MyAppBaseModel):
    class Meta:
        permissions =  (("foobar_childmodel", "Can foobar childmodel"),)

Two problems arise:

1. Although permissions currently may be inherited, the Options class does not currently implement %(class)s replacement like the RelatedField class does, so my permissions end up actually being stored in the database with %(class)s in the name and codename.
2. The way Meta attributes are currently processed in the ModelBase metaclass causes inherited permissions to be completely replaced if any explicit permissions are defined on the child class. So instead of can_view and can_foobar on ChildModel, I only get can_foobar.

This patch changes Django's behavior such that any explicit child class permissions would be appended to the inherited ones, rather than completely replacing them.

Also, I've added a backwards-compatible flag to the Meta options, 'inherit_permissions'. This flag would only be required in the case that one wanted Django's current behavior which is to discard base class permissions when explicit permissions are declared on the child class.

Example:

class MyAppBaseModel(models.Model):
    class Meta:
        abstract = True
        permissions = (("view_%(class)s", "Can view %(class)s"),)

class ChildModel(MyAppBaseModel):
    class Meta:
        permissions =  (("foobar_childmodel", "Can foobar childmodel"),)
        inherit_permissions = False

This would result in ChildModel only having the can_foobar permission (Django's current behavior). If you wanted to inherit/append the view_class
permission instead (proposed behavior), you could set the attribute to True or leave it out entirely.

This, of course, assumes that my desired behavior is what most other people would want. I suspect, but am not certain that this is the case.

Though a small change, I believe it requires a design decision.

Thanks!

[anonymous]

I think both of these improvements need to be implemented. I make heavy use of abstract classes and writing the permissions for each child model is a lot of redundant coding.

[Soby]

Updated patch that works on rev 16527. Also supports de-duping permissions and combining permissions from multiple inheritance on the model.

[Aymeric Augustin]

Change UI/UX from NULL to False.

[Aymeric Augustin]

Change Easy pickings from NULL to False.

[Anssi Kääriäinen]

Seems like good changes to me.

[Ilkka Hakkari]

I managed to write tests for the new functionality described in this ticket.

​https://github.com/derega/django/tree/ticket_10686

[Tim Graham]

These changes also need to be documented.

[Sergei Maertens]

I'm going to apply the patch to current master and add documentation updates.

[Sergei Maertens]

Applied the patch to current master and I've added documentation.

[Tim Graham]

​django-developers discussion which suggests to avoid the proposed inherit_permissions Meta option.

[Sergei Maertens]

I'm starting work on this again such that inherit_permissions is not needed.

Models inheriting from abstract models inherit the Meta, so unless permissions are being added in the concrete model, there is no boilerplate required. In the event that the concrete class also has custom permissions, the pythonic way is the way to go:

class Task(BaseTask):
    ...

    class Meta(BaseTask.Meta):
        permissions = BaseTask.Meta.permissions + (
            ('reassign_assignedtask', 'Can reassign assigned task')
        )

[Sergei Maertens]

Addition: it's not possible to inherit a concrete class' Meta per ​https://docs.djangoproject.com/en/1.9/topics/db/models/#meta-and-multi-table-inheritance

[Sergei Maertens]

​PR

[Tim Graham]

Comments for improvement on the PR.

[Sergei Maertens]

Processed the remarks, up for re-review

[Tim Graham]

Left some more comments.

[Sergei Maertens]

Processed comments - 1 comment was replied to on Github & no change made in docs: ​https://github.com/django/django/pull/6861#discussion-diff-74686863

[Sergei Maertens]

Note to self: the unit test should check that the correct permissions are created in the db, per:

​https://github.com/django/django/pull/6861#issuecomment-240427426

Worked on some cosmetic edits: ​http://dpaste.com/19R4PZE but I also noticed that this doesn't seem to create the correct permission in the database. For the pizza example in the docs I see things like "can_deliver_base" in the database.

[julian@pinabausch.org]

Dear community,

just picked this while figuring out how to build permission names dynamically.

Here’s a new PR: ​https://github.com/django/django/pull/15936

Open issues:

• Tim Graham commented that the code may be [generating faulty permissions](​https://github.com/django/django/pull/6861#issuecomment-240427426). I checked the behavior in a dummy project, but cannot confirm. I struggled to write a test for this, because it needs real migrations, real data etc. in the database. Please let me know if there’s an example in the existing tests that I can check (the advanced testing docs don’t mention “defining a real model in a testcase” either)
• Authors and version added are still missing – I’ll add this if it has a chance to get merged.
• (Changed to class argument to `model_name´ – I believe this is more consistent with content types & auth

[julian@pinabausch.org]

Thanks Mariusz Felisiak for being so responsive!

I’d love to hear your comment on this:

Tim Graham commented that the code may be [generating faulty permissions](​​https://github.com/django/django/pull/6861#issuecomment-240427426).
I checked the behavior in a dummy project, but cannot confirm. I struggled to write a test for this, because it needs real migrations, real data etc. in the
database. Please let me know if there’s an example in the existing tests that I can check (the advanced testing docs don’t mention “defining a real model
in a testcase” either)

There are quite a few nonsense commits – when you consider the main work done, please let me know. I’d like to squash the commits and add the co-authors before merging.

[Mariusz Felisiak]

I left comments on PR.