diff --git a/ayanova/src/views/ay-report-edit.vue b/ayanova/src/views/ay-report-edit.vue
index b29fbe24..566c5c27 100644
--- a/ayanova/src/views/ay-report-edit.vue
+++ b/ayanova/src/views/ay-report-edit.vue
@@ -131,24 +131,15 @@ import * as monaco from "monaco-editor";
 
 /*TODO:
 
-report selector
-  direct edit or render report from list
 
-Modify report editor to handle lack of data
-    
-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?
+  faster, but, it's logical to see what it would look like in reality by letting server render it then you know wysiwyg
+  However, when a user wants to quickly test a template out it would be better to do it locally.
+    hmm..
 
-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