From aaf0f70565c92e5290f9cf4916899de1c5ff3435 Mon Sep 17 00:00:00 2001 From: Radoslav Georgiev Date: Wed, 9 Apr 2025 11:07:38 +0300 Subject: [PATCH] Add a useful comment thanks to issue #170 --- README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.md b/README.md index 7d9b9f5..8fbc04e 100644 --- a/README.md +++ b/README.md @@ -168,6 +168,12 @@ This styleguide aims to: 1. Give you those "boxes". 1. Help you figure out your own "boxes", for your own specific context & needs. +Additionally, thanks to this comment - https://github.com/HackSoftware/Django-Styleguide/issues/170 - there's one additional way of looking at this: + +The way your app should behave (or as we call it - "business logic") should not be related to the way you interface with it (be it an API, a management command or something else) and this is a very clear line, where we want to separate our concerns. + +Of course, there are cases, where things can get intertwined, yet, a good baseline for thinking about this separation is - "core" vs. "interface". + --- > 🤔 Why not put your business logic in custom managers and/or querysets?