From 14026293e659cb8e20de445a8a1c04b260445fa1 Mon Sep 17 00:00:00 2001 From: mjumbewu Date: Sat, 8 Sep 2012 08:22:45 -0700 Subject: [PATCH] Updated DjangoCon US 2012 Sprints (markdown) --- DjangoCon-US-2012-Sprints.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/DjangoCon-US-2012-Sprints.md b/DjangoCon-US-2012-Sprints.md index 6e13131..5bf14d6 100644 --- a/DjangoCon-US-2012-Sprints.md +++ b/DjangoCon-US-2012-Sprints.md @@ -71,7 +71,7 @@ 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. -> 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 +> 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. I'm gonna try that approach out. - @mjumbewu ### Test out object-level permissions.