ayanova/devdocs/todo.txt

@@ -33,6 +33,24 @@ Also need a protocol for handling updating front and back
 
 # OUTSTANDING MAJOR AREAS TO BETA
 
+- Monaco editor, update it to latest if possible and add js validation setting seems to be built in but is not in effect:  
+    // validation settings
+    monaco.languages.typescript.javascriptDefaults.setDiagnosticsOptions({
+      noSemanticValidation: false,
+      noSyntaxValidation: false
+    });
+
+    This would have caught Joyce's errors in js code, also maybe there is a linter for other things too which woudl help with css issues etc
+
+
+- Report templates code
+  go through every report, look at javascript in preparedata and determine if any weirdnesses
+    for example the customer z_replaceCarriage return with space code is using an undeclared variable n (which is also redundant anyway)
+    there maybe issues that need to be fixed or performance things etc
+    can't just assume they are all correct
+    maybe a quick check is to lint them in a copy paste standalone file??
+      YES, make a test .js script page that is a "harness" for the code then copy paste into it and it will show the errors
+
 - Features	
 	Roles
 		Before beta take the time to login as each role and confirm that they can do the tasks they need to