From 702ca6d287be764eb9b8c68968095dd9e5bad015 Mon Sep 17 00:00:00 2001 From: Radoslav Georgiev Date: Fri, 21 Jan 2022 14:08:14 +0200 Subject: [PATCH] Add emojis --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index f285e8f..beb4dbd 100644 --- a/README.md +++ b/README.md @@ -105,7 +105,7 @@ The general idea is to "separate concerns" so those concerns can be maintainable ## Why not? -> Why not put your business logic in APIs / Views / Serializers / Forms? +> 🤔 Why not put your business logic in APIs / Views / Serializers / Forms? Relying on generic APIs / Views, with the combination of serializers & forms does 2 major things: @@ -125,7 +125,7 @@ This styleguide aims to: --- -> Why not put your business logic in custom managers and/or querysets? +> 🤔 Why not put your business logic in custom managers and/or querysets? This is actually a good idea & you might introduce custom managers & querysets, that can expose better API, tailored to your domain. @@ -146,7 +146,7 @@ With all that in mind, custom managers & querysets are very powerful tool and sh --- -> Why not put your business logic in signals? +> 🤔 Why not put your business logic in signals? From all of the available options, perhaps, this one will lead you to a very bad place very quickly: