Alternative to `RulesModelBase` in DRF to manage dependency on this library.

I’m working on a Django DRF project, and while implementing the rules, I feel like inheriting from RulesModelBase creates a really heavy dependency on this library.

I’m trying to make it so that the rules dependency only affects the views, and not go all the way to the models.

From what I can gather, the views have access to the current user, and the objects. The predicates get both the user and the permission object as parameters, so it feels like it would be possible.

Has anyone dealt with similar issues than this?

https://github.com/dfunckt/django-rules#permissions-in-django-rest-framework

Of course, it also requires you to declare your models as described in Permissions in models.

[sergioisidoro]

Sure, I’ll post a PR for this. Actually maybe I can make 2:

• One PR, which is the simplest, to abstract the get_permission_form_model making it overridable in the mixin
• Another PR based on the first one with these larger changes.

We can move the discussion there as well, since it’s easier to discuss things with concrete code 😃

Thanks for taking the time and attention on this! Really appreciate it!

[dfunckt]

Okay, I totally see the use-case and agree in principle that this would be great to have but I need to spend some time to check the existing code and your proposal in more depth. If you’re keen to PR stuff in the meantime, feel free and we’ll take it from there.