From d5b7e45e5a0cdedf9389c9bc7497463374f5b1cb Mon Sep 17 00:00:00 2001 From: mjumbewu Date: Sat, 8 Sep 2012 16:32:12 -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 d976ac4..6ce2f23 100644 --- a/DjangoCon-US-2012-Sprints.md +++ b/DjangoCon-US-2012-Sprints.md @@ -71,7 +71,7 @@ I think the base ModelResource will probably need to be composed of `APIView` Dj > 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 -[Pull request](https://github.com/tomchristie/django-rest-framework/pull/254) - @mjumbewu +**[Pull request](https://github.com/tomchristie/django-rest-framework/pull/254) - @mjumbewu** ### Test out object-level permissions.