encode/django-rest-framework
1
1
Fork 0
mirror of https://github.com/encode/django-rest-framework.git synced 2024-11-24 10:34:03 +03:00
Code Issues Packages Projects Releases Wiki Activity

Updated DjangoCon US 2012 Sprints (markdown)

mjumbewu 2012-09-08 08:22:13 -07:00
parent 2ec426c43b
commit 7e5d522674
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
DjangoCon-US-2012-Sprints.md

@ -71,6 +71,8 @@ Resources are view-like classes that implement everything except the actual `.ge
I think the base ModelResource will probably need to be composed of `APIView` Django's `MultipleObjectMixin` *and* `SingleObjectMixin`, plus *all* the REST framework mixins. I think the base ModelResource will probably need to be composed of `APIView` Django's `MultipleObjectMixin` *and* `SingleObjectMixin`, plus *all* the REST framework mixins.
> Maybe instead it can just be derived from `object`, and act as a mixin itself. Then, the routers would just construct classes that derive from the appropriate mixins as needed. - @mjumbewu
### Test out object-level permissions. ### Test out object-level permissions.
REST framework should now support object level permissions. (See `SingleObjectBaseView.get_object()` in `generics.py`.) Using a view with `DjangoModelPermissions`, install `django-guardian` and see if you can get everything playing together nicely. If so, the Authentication documentation should be updated to reflect that. REST framework should now support object level permissions. (See `SingleObjectBaseView.get_object()` in `generics.py`.) Using a view with `DjangoModelPermissions`, install `django-guardian` and see if you can get everything playing together nicely. If so, the Authentication documentation should be updated to reflect that.