This commit is contained in:
2020-10-22 23:20:28 +00:00
parent 18758d8fdb
commit 7c237af04e

View File

@@ -3,18 +3,29 @@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
### BIG ITEMS ###
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
https://www.npmjs.com/package/json-2-csv
From extensions?
(because it's a single or list thing)
Decide, do we need this now?
What purpose does it serve our potential customers?
Isn't it really just used to get out of AyaNova into another package?
PLAN:
Export via extensions menu system
Export as either json or csv supported
todo: Modify extensions to automatically assume *all* record ID's from the grid list just as report does when nothing selected
so it shouldn't say zero items selected, it should say "All records in list" instead
todo: Modify extensions that exist to work with all id's in the datalist instead if none selected (just like report does, re-use report code)
todo: SERVER - make a IExportableObject that mirrors IReportAble so that can control what exactly can be exported
todo: SERVER - make a biz and route for export that mirrors report objects
Export file is downloadable for a few minutes once prepared at server just like report and client triggers download once it gets the file name back
Export as JSON or as CSV https://github.com/JoshClose/CsvHelper
todo: import
This is in it's own UI area I guess
Kind of a tricky one, do we really need it up front in initial release?
Should import it's own export I guess, but what would be the usage of that?
Import should really go through the api and just create the objects via api?
like v8Import does
DASHBOARD / KPI / BIZ METRICS
@@ -30,6 +41,14 @@ todo: DASHBOARD
I guess a wrapper over the graphs so they can be called directly during server render as well as from vuetify at client
ON HOLD
=-=-=-=-
todo: breaking change in latest vuetify with integer bound to v-text-field have kept this version awaiting fix, reported
https://github.com/vuetifyjs/vuetify/pull/12451
If not fixed in a timely manner can downgrade to the build before this one
todo: hide swagger logo and branding in api explorer
Is this really that important?
also, in the docs is a section specifically saying I should do something because I'm using newtonsoft json not microsoft built in
@@ -42,13 +61,6 @@ todo: service workers for monaco going in root of website folder, must be a conf
awaiting reply, if nothing by the time I get here then delete and wait for email notification or if I care enough again to bother with it (cosmetic)
ON HOLD
=-=-=-=-
todo: breaking change in latest vuetify with integer bound to v-text-field have kept this version awaiting fix, reported
https://github.com/vuetifyjs/vuetify/pull/12451
If not fixed in a timely manner can downgrade to the build before this one
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@ ROADMAP STAGE 5 - FINALIZE ALL NON BIZ OBJECT SPECIFIC FUNCTIONALITY
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@