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.
Mixins
Simple business logic functions should in models or managers. When there's a lot of them, the can be split in mixins.
# logic.py
class EventLogic(object):
def start(self):
if self.condition():
# ...
# models.py
class Event(models.Model, EventLogic):
name = models.CharField()
# ...Custom exceptions
For business logic errors you should declare custom exception classes. It's not fun to understand what this specific IntegrityError means.
Generic views
When all logic is in model and can throw, say, BusinessLogicException, we can write views like this:
from django.contrib import messages
def event_action(requets, event_id, action):
# event = get_object_or_404(...)
try:
getattr(event, action)(request.user)
except BusinessLogicException, e:
messages.warning(request, e.message)
return redirect(request.POST.get('next') or event)Subscribe for the news and updates
Tired of boring programming courses where you're forced to read thick textbooks and write code that's never used? Need a platform that makes learning fun and exciting? Then you're in the right place!
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.
Programmatic generation of PDF files is a frequent task when developing applications that can export reports, bills, or questionnaires. In this article, we will consider three common tools for creating PDFs, including their installation and converting principles.
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.
There was a task to submit form with ajax, with server side validation of course. Obvious solution is to do validation and return json with erros. I didn't like idea of writing separate view for validation and then inserting errors in form html on client side. Especially since I already had a generic template for django form with errors display. In this article I'll describe how I solved the task.