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
The article highlights common test case mistakes, offers ways to fix them, and provides practical tips to improve and optimize test cases.
We reviewed the best payment gateways in 2020. Here’s our comparison of their features, advantages, and disadvantages.
We often handling API server updates including backwards-incompatible changes when upgrading web applications. At the same time we update the client part, therefore, we did not experience any particular difficulties.
In this article we will write a small library for pulling metadata and creating a preview for a site just like Slack does.
When we use css-sprites it's important to make browser cache them for longest period possible. On other hand, we need to refresh them when they are updated. This is especially visible when all icons are stored in single sprite. When it's outdated - entire site becomes ugly.
In my current project I had a task to use twitter API. Twitter uses OAuth for authentication, which is pretty dreary. To avoid fiddling with it all the time, I've moved authentication to decorator. If key is available - nothing happens, just view is launched as usual. It's convenient that there's no need for additional twitter settings in user profile. Code is in article.