This commit is contained in:
2020-07-01 23:51:34 +00:00
parent ad19385ca2
commit bbd41bbeab
2 changed files with 9 additions and 6 deletions

View File

@@ -3,14 +3,12 @@
PRIORITY - ALWAYS Lowest level stuff first, i.e. TODO at server, api route changes etc then back here in order lowest level first as affects the most stuff exponentially so best to do it early
=-=-=-=-
todo: Translation list should have default sort by key descending when open it
todo: VERIFY FIXED JobExclusiveWarning missing translation at server
todo: VERIFY FIXED Job queue form has no column headers for jobs, should it?
todo: ops metrics "other" database files oddly large by orders of magnitude above others
what up?
todo: default sort order for default data list views specified? (see eventdatalist for example)
todo: set network speed in dev console of firefox to regular 2g then go through all forms and confirm all still works as this will expose any await issues
todo: consider moving canDuplicate etc from a "computed" property into methods (just drag and drop)
in fact, look for all computed and consider them carefully because computed seems to be bullshit
@@ -44,6 +42,8 @@ todo: error http://localhost:8080/adm-global-select-templates pick Customer get
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextExceptionFilterAsync>g__Awaited|25_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
todo: rename v8 export plugin to v8 Migrate
it's more accurate and easier to grasp for people (plus it rhymes)
todo: Migrate to v8 plugin needs to work with a trial database as well as a licensed database
It should check if a trial or not and give heavy warning if not
kind of cool if it checked for a recent backup before doing anything damaging
@@ -51,6 +51,8 @@ todo: Migrate to v8 plugin needs to work with a trial database as well as a lice
todo: ability to mass tag items from list CLIENT UI
- See bulk jobs added to Attachment list
- Very likely this will be more appropriate as a per form menu option as it will require specific needs per type, or maybe not, just spitballing
- some kind of generic or copyable light interface for any mass / bulk job?
this will get re-used for other stuff undoubtedly down the road
- also a good way to do an initial implementation of a mass ops UI code
@@ -89,6 +91,7 @@ todo: History - MORE button not showing? Was looking at administrator history f
todo: readonly on all forms make sure it's ok, because on customize form I see no save but can edit
- (logged in as bizadminlimited)
todo: when server is in ops only mode the client needs a way to prevent people from opening things that they shouldn't.
First of all, test and see what happens in NON dev mode at the client
for example if a admin logs in they can and should access serverstate page and some other stuff ops related, but all other routes should be locked out
I know the server will send a 404 or something but maybe that needs tweaking to show a proper message at the client or just not show those options or something?
(part of long polling maybe??)
@@ -129,6 +132,7 @@ todo: Login form customizable for logo etc?
Give this a serious thought because it seems like we might be being shitty to ourselves if we support this
todo: Customer UI pages ability to add analytics tracking codes:
CORS implications?
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3574
todo: ADM-USER awaiting customer, headoffice id, etc for those usertypes
@@ -152,8 +156,7 @@ todo: NOW THAT FORM IS THERE MOSTLY, CLEAN UP CODE FOR RE-USE in many other form
- What I mean is, for example, a text entry field could be standardized then re-used as a component if it's props and settings take up so much space etc
- formstate shit is also menu shit really so can they be combined somehow, like present two sets of menu options one read only and one fully read-write?
- some forms will have special needs but could handle them outside of the regular boilerplate shit?
todo: rename v8 export plugin to v8 Migrate
it's more accurate and easier to grasp for people (plus it rhymes)
todo: Investigate Workorder structure and datagrid see case https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3768
todo: Document in user manual the Widget form as an example with instruction on how to use the various controls etc
- "Anatomy of a AyaNova Form"

View File

@@ -2,7 +2,7 @@
<v-row v-if="this.formState.ready">
<gz-error :errorBoxMessage="formState.errorBoxMessage"></gz-error>
<v-col cols="12">
<v-btn @click="getDataFromApi" class="mt-1 mb-n6">
<v-btn @click="getDataFromApi">
<v-icon>fa-sync</v-icon>
</v-btn>
<v-simple-table>