ayanova/devdocs/todo.txt

@@ -8,10 +8,9 @@ MISC ITEMS THAT CAME UP
 
 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
+	not actually users as far as I can tell, were removed, need to be re-added back again
+
 
-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:
@@ -28,10 +27,8 @@ todo: customer users and regular users really need to reconsider not using a sta
 	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
+	AT LEAST put a wait spinner on that page
 
-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
@@ -41,7 +38,7 @@ todo: deleting customer must attempt to delete the following as they are entered
 
 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
@@ -53,7 +50,7 @@ todo: No roles defined Users can login
 todo: Case 3595 Mass delete extension
 	Do this early as it will be copied over and over again
 
-todo: seeder notification seeding completed?
+
 
 ............................................................