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

@@ -136,28 +136,34 @@ import * as monaco from "monaco-editor";
 
 /*TODO:
 
-
-need to modify reportData data object to accept meta data outside of the main data collection
-  so can add all the bits that would appear on report potentially or be used on page like
-  datalist name, filter options, what have you
-  also ayReportData object, should it be named something else?  Does it even matter?
-
-need to ensure easy api access from report script, perhaps pass creds token into report along with report?
-  creds as meta data?
-
+this next one because it would be helpful for development testing now
 Ability to export / download and save entire report template as an independent object / file
   and import again
   .ayr8?
 
+Logo as helper in handlebars?  that would be easy peasy I think if it's supported
 
 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
 
 Make a working template with api methods being called
-  export as example
+  api helper js injected to work with api methods, automatically uses the bearer token in client meta data
+  export as example and also document
 
-Start thinking about currency formatting and date/time formatting etc.
-Maybe client can pass a function to server, or server can use exact same libs but can be initiated with specific locale from client?
+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
+
+docs
+  document basics
+  handlebars, links to hb etc
+  built in helpers sb documented
 
 
 build release for joyce to play with and give feedback