Skip to content

Commit aaf0f70

Browse files
committed
Add a useful comment thanks to issue #170
1 parent 2396ac5 commit aaf0f70

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -168,6 +168,12 @@ This styleguide aims to:
168168
1. Give you those "boxes".
169169
1. Help you figure out your own "boxes", for your own specific context & needs.
170170

171+
Additionally, thanks to this comment - https://github.com/HackSoftware/Django-Styleguide/issues/170 - there's one additional way of looking at this:
172+
173+
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.
174+
175+
Of course, there are cases, where things can get intertwined, yet, a good baseline for thinking about this separation is - "core" vs. "interface".
176+
171177
---
172178

173179
> 🤔 Why not put your business logic in custom managers and/or querysets?

0 commit comments

Comments
 (0)