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
In the previous article, we learned about test analysis for a product in general, and now we are ready to go further and look at test analysis for specific features.
In this article I’m going to show how to declare custom prosemirror node, how to render it with toDom method and how improve that with custom NodeView using React component.
We have reviewed the top web frameworks for server and client-side development and compared their pros and cons. Find out which one can be a great fit for your next project.
In this beginners friends article I'll explain how to make authentication with Google account on your Django site and how to make authentication for you REST API.
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.
As you know, model managers can be overriden in Django. It's convenient to add custom filtration method.