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
Web development has undergone significant changes over the past five years due to a combination of technological advancements and changing user needs. Let's look at the drivers of these changes and the key technologies that have played a decisive role.
One of our ongoing projects, Neptyne, introduces an Excel-like grid written in React. We used a library to apply virtual scroll to it, but we stumbled upon a problem with fixed rows and columns inside the grid. Here I would like to describe this problem, how it occurs, and how we handled it.
Django ORM is a very abstract and flexible API. But if you do not know exactly how it works, you will likely end up with slow and heavy views, if you have not already. So, this article provides practical solutions to N+1 and high loading time issues. For clarity, I will create a simple view that demonstrates common ORM query problems and shows frequently used practices.
Quite often we have to write paginated or filtered blocks of information on page. I created a decorator that would automate this process.
As you know, model managers can be overriden in Django. It's convenient to add custom filtration method.
For local project settings, I use old trick with settings_local file:try:from settings_local import \*except ImportError:passSo in settings_local.py we can override variables from settings.py. I didn't know how to supplement them. For example how to add line to INSTALLED_APPS without copying whole list.Yesterday I finally understood that I can import settings from settings_local:# settings_local.pyfrom settings import \*INSTALLED_APPS += (# ...)