Most of the time your Django views look like this:

def my_view(request, args):
    # deal with args
    # deal with permissions
    # do some useful stuff
    # deal with rendering
    return an http response

I think it's a bit silly to continuously copy/paste boring parts and that's exactly the place where decorators can be powerful.


Imagine decorators like that:

def my_view(request, instance):
    # do some useful stuff
    return a context dict


  • from_object which deals with arguments and return an instance
  • owner_required which verifies if the request.user is the owner of the retrieved object
  • as_html which renders the context dict returned as an http response

You can of course set a lot of as_* decorators (as_json, as_rdfxml and so on) applied in urls in order to use the same view.

There is some basic code for now if you need to read code to better understand how it works (like me), do not hesitate to discuss.


Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.