ayanova/src/views/ay-report-edit.vue

@@ -135,14 +135,10 @@ import * as monaco from "monaco-editor";
 //https://github.com/egoist/vue-monaco/blob/master/src/MonacoEditor.js
 
 /*TODO:
+Translation:
+  Provide method in report that accepts an array of strings and then fetches them in pre-render for use with the ayT hb helper afterwards which operates only on pre-fetched items
+  Since user's will likely rarely use translations themselves when they make their own reports it's not critical that it be super easy to use so a simple function call in pre-render will do it.
 
-Executive decision, no longer attach reports to emails...ever.  User must log in 
-  this is to avoid a lot of fragile code but also for:
-  Security, email hassle avoidance (attachments increasingly failing), etc etc
-
-
-determine course of action to handle locale keys list for report based on fields in data source
-  I'm thinking of replicating the Client translation.js code for this as it's simple and tested
 
 An error when direct rendering brings UI down unlike during render and error when in report designer, fix it
 
@@ -152,27 +148,20 @@ Add sanitize html for Marked markdown helper as in Wiki control
 
 Is the report list filtered by roles?  It should not present reports that a user is not permitted to use by role.
 
-When in report designer it should show how the html generated by the renderer as a diagnostic assistant
-
-Make up sample reports for widget that show off the basics including logo etc
-
-make them auto generate (import from files?) with sample data in seeder
+When in report designer it would be useful to show the html generated by the renderer as a diagnostic assistant
+  Also the script that will be executed minus the hb and marked etc if possible
 
 "tab" button color doesn't follow pre-defined colors, use highlight instead
 also make the data tab button grayer looking so it's clearer that it's different than the rest
 
-Make a working template with api methods being called
-  api helper js injected to work with api methods, automatically uses the bearer token in client meta data
-  export as example and also document
+INITIAL SAMPLE REPORTS
+  Make up initial sample reports for widget that show off the basics including logo etc
+  make them auto generate (import from files?) with sample data in seeder
+  Default example working template with api methods being called generated automatically
 
-Example with currency formatting and date/time formatting etc.
-  Use same libs as at client with built in helpers using client meta data 
-  think about scenario of forcing locale values when client is fucked up or server doesn't know what to use?? hmmm...maybe need to save the locale with the report design for safe keeping and server use
-  System needs a default or override for the locale, ideally though it would just work because it would take some value from somewhere, maybe the server local defaults for the headless chrome
-  or maybe it's a server setting where the biz admin can say "use my current settings at client as the default"
-  tricky but doable I guess with some server defaults
-  So the server render report code needs to substitute for client meta when there is none by impersonating the user the report is notifying to and using their creds maybe?
-  Needs some thinking through
+  Example with currency formatting and date/time formatting etc included automatically.
+    Use same libs as at client with built in helpers using client meta data 
+    Since reports will only ever be rendered on Client demand can stick with that system for now and replicate at headless chrome that same process in hb helpers
 
 docs
   document basics