From b8b9ab05a93e41def65a85542757f22a3c4a0001 Mon Sep 17 00:00:00 2001
From: einatnielsen <einat.bertenthal@nielsen.com>
Date: Wed, 1 Jul 2020 10:26:38 +0300
Subject: [PATCH 1/2] feat: high level clean code content

---
 design/Frontend-Design.md | 47 ++++++++++++++++++++++++++++++++++++++-
 1 file changed, 46 insertions(+), 1 deletion(-)

diff --git a/design/Frontend-Design.md b/design/Frontend-Design.md
index 6b81d9c..7ad111c 100644
--- a/design/Frontend-Design.md
+++ b/design/Frontend-Design.md
@@ -1 +1,46 @@
-# TBD
\ No newline at end of file
+### Clean code
+
+#### Variables
+Give meaningful names to variables
+
+#### Functions
+1. Function name should describe what it does.
+2. A function should do only one thing.
+3. Limit the amount of function parameters, preferably two. if you need more you can send the parameters inside an object.
+4. If you find yourself writing the same code more than once, even if its a little bit different, try to generalize it in to a function.
+5. Functions should be pure
+
+#### Classes
+
+#### React components
+1. Make your React component as short as possible
+2. Name Your Components Using Standard Naming Conventions
+3. Reduce the number of props to the minimum
+4. Put Independent Functions Outside of Your Custom Hooks
+5. Split your components to container and presentational components
+6. Folderize Your Components
+
+#### DTY
+DRY is an acronym that stands for "Don’t Repeat Yourself."
+If you find yourself writing the same code in different places, consider writing it only once and just reuse it, whether as a function or as a component.
+
+#### KISS
+KISS is an acronym that stands for "Keep it simple stupid."
+
+#### SOLID
+Single Responsibility Principle (SRP)
+Open/Closed Principle (OCP)
+Liskov Substitution Principle (LSP)
+Interface Segregation Principle (ISP)
+Dependency Inversion Principle (DIP)
+
+
+#### Testing
+When you write your code, you should write it in a way it would be easy to test it. make your code predictable and testable.
+
+#### Error handling
+
+#### Comments
+If you write clean code, it should be self commenting.
+
+#### Type script

From bda17cb52eb3a197f88c51757b33b6234400f3dc Mon Sep 17 00:00:00 2001
From: einatnielsen <einat.bertenthal@nielsen.com>
Date: Wed, 1 Jul 2020 10:48:00 +0300
Subject: [PATCH 2/2] fix: typo

---
 design/Frontend-Design.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/design/Frontend-Design.md b/design/Frontend-Design.md
index 7ad111c..5fb56b5 100644
--- a/design/Frontend-Design.md
+++ b/design/Frontend-Design.md
@@ -20,7 +20,7 @@ Give meaningful names to variables
 5. Split your components to container and presentational components
 6. Folderize Your Components
 
-#### DTY
+#### DRY
 DRY is an acronym that stands for "Don’t Repeat Yourself."
 If you find yourself writing the same code in different places, consider writing it only once and just reuse it, whether as a function or as a component.