ayanova/devdocs/todo.txt

@@ -5,6 +5,9 @@
 
 
 todo: can it just scan for locale keys and prefetch them rather than user having to add up front?
+todo: a script error when just running a report from the report selector acts weird
+	Test with dev mode off to confirm it won't show it in the UI
+	Should show the error in the UI
 
 TODO:  Report confirmation checklist
 	- page breaks properly EXAMPLE NEEDED
@@ -44,6 +47,9 @@ TODO:  Report confirmation checklist
 todo: Open source credit area in UI
 	acknowledgements etc
 
+
+
+
 todo: export from grid to xls, csv etc.
 	I'm thinking perhaps also a secondary ability to make report templates that are actually intended for export to xls or whatever as an additional feature
 	but the easiest thing for people would be a straight export of grid data from grid, perhaps using the reportdata system since it pulls in all the bits needed for full data rather than just id links
@@ -326,6 +332,13 @@ Plan the order of criticality for extensions
 @@@@@@@@@@@@@@@ ROADMAP STAGE 9 - RELEASE
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
 
+todo: ARCHIVE ALL DEPENDENCIES
+	Get all code for all 3rd party libs used for front and back of AyaNova 8
+	Need to store that in an archive somewhere just in case
+	Needs to be done with each release so can go back to that if necessary
+	Going to be big, maybe archived to all storage drives locally and burned to a dvd?
+	If check into the repo it will be an issue probably but you never know
+
 TODO: CSP Policy that should be enabled at server?
 	I had to add per this: https://docs.telerik.com/kendo-ui/troubleshoot/content-security-policy#content-security-policy
 	to my csp because I kept getting errors in client end debug console mentioning csp issues