In UNIX way, each view should solve single task. This is good idea, but sometimes we need to mix logic of different views on same page. Filter, sort, paginate, or, for example, add comment on product page. In this article I'll show how we can mix such multiple views.
Idea
We can write views as decorators.
Example
Simplified filtration can look like this:
from django.views.generic.list_detail import object_list
def filtered_list(request, filterset_class, queryset, *args, **kwargs):
filterset = filterset_class(request.GET)
queryset = filterset.filter(queryset)
kwargs['extra_context']['filterset'] = filterset
return object_list(request, queryset, *args, **kwargs)This is simple and straightforward, but in order to add some tricky pagination, we have to copy entire view and add more code to it.
Instead, we can create decorator like this:
def filtered(view):
def wrapped(request, filterset_class, queryset, *args, **kwargs):
filterset = filterset_class(request.GET)
queryset = filterset.filter(queryset)
kwargs['extra_context']['filterset'] = filterset
return view(request, queryset, *args, **kwargs)
return wrappedResult
Assuming, that we have similar decorators, sorted и paginated, we can easily combine them:
@filtered
@paginated
def technic_list(*args, **kwargs):
# ...Or even like this, in lisp style:
url(r'^technic/$', filtered(sorted(paginated(object_list))), {
'filterset_class': FilterSet,
# ...
}, name='technic_list'),Subscribe for the news and updates
In one of our recent projects, we had an interesting case: the whole application was built around an interactive map for a fairly large shopping mall, and the main goal of the system was to plot the closest route to a user-selected destination.
Dive into our guide to RESTful API best practices
Once we received an interesting task from a client. They needed to allow their users to upload a 3D model of the building and show it in a timelapse video from the construction site.
Learn how to use "OR" and "AND" queries efficiently in Django without using database models Q. Enhance your query-building skills. Dive in now.
In my recent project there was a lot of data business logic, so I had to organize this code somehow. In this article I'll describe a few hints on how to it.
Everybody knows about permalink, but it's usually used only in get_absolute_url. I prefer to use it for all related model urls.class Event(models.Model):# ...@models.permalinkdef edit_url(self):return ('event_edit', (self.pk, ))And then in template:<a href="{{ event.edit_url }}">Редактировать событие</a>