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

@@ -114,6 +114,32 @@ import * as monaco from "monaco-editor";
 //vue-monaco component source
 //https://github.com/egoist/vue-monaco/blob/master/src/MonacoEditor.js
 
+/*TODO:
+Get data from list
+  needs work at this end in widget list form (or is it in the data-list control?)
+
+template roundtrip save and open template from server
+
+decision: render here or at server in designer for preview of report?
+  going to happen a lot during design build cycle, faster to do locally?
+
+decision: how to handle opening report templates in the UI - should every reportdata object have built in fake data stored with report template?
+  It will be a bit shittier if can't open the report template directly and see *something* in it like from history and event log
+    Maybe if a type but no records are provided it can infer and just find a record to populate with like picks the first widget that exists or something?
+  Or, maybe it just saves the initial data used to last edit the report - NO this would expose real data in the editor which could be a rights issue situationally
+  in v7 you can't just open a report template directly can you?
+
+  Or, maybe it just handles that situation in the editor, no data, no problem, just can't preview the report, can only edit / view the template, and have to go through an object to view it with data
+    This seems like a good interim way to handle it and also easy peasy to code, just accepts if it doesn't have the idlist or whatever and disables preview mode
+
+
+working widget template
+
+print / preview coded to work with saved report and renders
+
+build release for joyce to play with and give feedback
+
+*/
 const FORM_KEY = "ay-report-edit";
 let JUST_DELETED = false;
 let editor = null;