Added tags & categories + cleanup

content/docs/NAVPatterns/3-cal-coding-guidelines/design/_index.md

@@ -1,6 +1,8 @@
 +++
 title = "Design"
 weight = 490
+tags = ["C/AL"]
+categories = ["Best Practice"]
 +++
 ## C/AL Coding Guidelines
 

content/docs/NAVPatterns/3-cal-coding-guidelines/design/by-reference-parameters/index.md

@@ -1,6 +1,8 @@
 +++
 title = "By Reference Parameters"
 weight = 280
+tags = ["C/AL"]
+categories = ["Best Practice"]
 +++
 Do not declare parameters by reference if their values are not intended to be changed.
 

content/docs/NAVPatterns/3-cal-coding-guidelines/design/class-coupling/index.md

@@ -1,6 +1,8 @@
 +++
 title = "Class Coupling"
 weight = 320
+tags = ["C/AL"]
+categories = ["Best Practice"]
 +++
 Do not write functions that have high class coupling. This makes the code hard to maintain.
 

content/docs/NAVPatterns/3-cal-coding-guidelines/design/cyclomatic-complexity/index.md

@@ -1,6 +1,8 @@
 +++
 title = "Cyclomatic Complexity"
 weight = 460
+tags = ["C/AL"]
+categories = ["Best Practice"]
 +++
 Do not write functions that have high cyclomatic complexity. This makes the code hard to maintain.
 

content/docs/NAVPatterns/3-cal-coding-guidelines/design/encapsulate-local-functionality/index.md

@@ -1,5 +1,7 @@
 +++
 title = "Encapsulate Local Functionality"
 weight = 530
+tags = ["C/AL"]
+categories = ["Best Practice"]
 +++
 Any function used local must be defined as local.

content/docs/NAVPatterns/3-cal-coding-guidelines/design/findset-findfirst-findlast/index.md

@@ -1,6 +1,8 @@
 +++
 title = "FINDSET FINDFIRST FINDLAST"
 weight = 600
+tags = ["C/AL"]
+categories = ["Best Practice"]
 +++
 FINDSET, FIND('+') or FIND('-') should only be used when NEXT is used and vice versa.
 

content/docs/NAVPatterns/3-cal-coding-guidelines/design/initialized-variables/index.md

@@ -1,6 +1,8 @@
 +++
 title = "Initialized Variables"
 weight = 660
+tags = ["C/AL"]
+categories = ["Best Practice"]
 +++
 Variables should always be set to a specific value, before they are used.
 

content/docs/NAVPatterns/3-cal-coding-guidelines/design/maintainability-index/index.md

@@ -1,6 +1,8 @@
 +++
 title = "Maintainability Index"
 weight = 770
+tags = ["C/AL"]
+categories = ["Best Practice"]
 +++
 [Maintainability Index][anchor0]: Do not write functions that have a very low maintainability index. This makes the code hard to maintain.
 

content/docs/NAVPatterns/3-cal-coding-guidelines/design/parameter-placeholders/index.md

@@ -1,6 +1,8 @@
 +++
 title = "Parameter Placeholders"
 weight = 920
+tags = ["C/AL"]
+categories = ["Best Practice"]
 +++
 The number of parameters passed to a string must match the placeholders.
 

content/docs/NAVPatterns/3-cal-coding-guidelines/design/static-object-invocation/index.md

@@ -1,6 +1,8 @@
 +++
 title = "Static Object Invocation"
 weight = 1160
+tags = ["C/AL"]
+categories = ["Best Practice"]
 +++
 Call objects statically whenever possible. It reduces extra noise and removes extra variables. Downside: changing the name of the object which is called statically will need a code update. 
 

content/docs/NAVPatterns/3-cal-coding-guidelines/design/unreachable-code/index.md

@@ -1,6 +1,8 @@
 +++
 title = "Unreachable Code"
 weight = 1310
+tags = ["C/AL"]
+categories = ["Best Practice"]
 +++
 Do not write code that will never be hit.
 

content/docs/NAVPatterns/3-cal-coding-guidelines/design/unused-initialized-variables/index.md

@@ -1,6 +1,8 @@
 +++
 title = "Unused Initialized Variables"
 weight = 1320
+tags = ["C/AL"]
+categories = ["Best Practice"]
 +++
 The value assigned to a variable must be used. Else the variable is not necessary. 
 

content/docs/NAVPatterns/3-cal-coding-guidelines/design/unused-variables/index.md

@@ -1,6 +1,8 @@
 +++
 title = "Unused Variables"
 weight = 1330
+tags = ["C/AL"]
+categories = ["Best Practice"]
 +++
 Do not declare variables that are unused.
 

content/docs/NAVPatterns/3-cal-coding-guidelines/design/variable-capacity-mismatch/index.md

@@ -1,6 +1,8 @@
 +++
 title = "Variable Capacity Mismatch"
 weight = 1410
+tags = ["C/AL"]
+categories = ["Best Practice"]
 +++
 Do not assign a value to a variable whose capacity is smaller.
 

content/docs/NAVPatterns/3-cal-coding-guidelines/design/with-scope-name-collision/index.md

@@ -1,6 +1,8 @@
 +++
 title = "WITH Scope Name Collision"
 weight = 1450
+tags = ["C/AL"]
+categories = ["Best Practice"]
 +++
 Do not use the WITH scope when it has a variable whose name is the same as a local variable. This can lead to wrong code assumptions.