From 8795097b9e5830396929e688643e06d550035e09 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Fri, 4 Dec 2020 20:49:05 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 25 +++++++++++++++++++++++-- 1 file changed, 23 insertions(+), 2 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index a4ff8914..a951e966 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -6,9 +6,13 @@ MISC ITEMS THAT CAME UP -todo: CustomerFull user can't login to seeded database, something must be fucked up, maybe because I need to tie it to an actual customer? +todo: CustomerFull && CustomerLimited && HeadOffice seed user can't login to seeded database, something must be fucked up, maybe because I need to tie it to an actual customer? When fixed re-run smoke e2e test which detected this and hung up on it +todo: SEEDER HUGE + This results in a metric fuck-ton of contact users since each customer creates one in addition to headoffice + Add a randomizer check when huge and only generate contacts for 10% of them + todo: if list view not found / deleted when grid list form is opened rather than erroring with object/object it should handle more elegantly: possibly show proper error but for sure select the no filter option automatically @@ -18,6 +22,16 @@ todo: if list view not found / deleted when grid list form is opened rather than maybe the local cache should be checked on login first and cleaned up? or I guess on demand is best since it's not eating up bandwidth +todo: customer users and regular users really need to reconsider not using a standard grid, + seeded huge basically dies waiting + However, how real is that scenario in the first place? + Ideally though for many reasons it should be a regular datagrid + Look into it, find out why it isn't and can it be implemented? + Also roles could then show on the customer-user grid which would be handy for some + +todo: DOCS + big performance tip: Disable ad-blocker type extensions on AyaNova + we do not serve any ads ever and it slows down considerably a big application todo: deleting customer must attempt to delete the following as they are entered "in" form and not selected externally so they are part of Customer and should delete with it: customer notes @@ -29,10 +43,17 @@ todo: deleting HeadOffice must attempt to delete all contacts too todo: seeded user names look stupid with the numbers in them, change that so unique is done but without that nonsense +todo: No roles defined Users can login + Customer user with no roles can login and gets a CSR list screen + regular user with no roles can login and gets the evaluation screen + but shouldn't see that either or at least not be able to do anything serious there + Ideally they should be able to login and see their own home stuff and notifications and maybe memos, but nothing else + Initialize.js needs tweaking + todo: Case 3595 Mass delete extension Do this early as it will be copied over and over again - +todo: seeder notification seeding completed? ............................................................