From 3226bda51c813094ea5e2d8f3e7c58f1cae23cd7 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Tue, 30 Mar 2021 00:28:49 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 8cb82a87..550107fb 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -210,7 +210,23 @@ todo: many biz objects are not using new PUT methodology -CURRENTLY DOING: workorder - first pass of porting models over, then will go through cases and adjust models as necessary for anything missed in first pass +CURRENTLY DOING: workorder back end + - first pass at back end to modernize the techniques used (asnotracking etc) + - ensure all objects are represented + - code rudimentary routes for all + - make minimal front end enough for POC wokorder->woitem->one granchild collection + - test out, confirm can CRUD as planned independantly and all at once + - will need some dirty fields and viz fields likely added to models so go minimal route as possible to POC it + - once pass this step then second pass at new features that affect models (not necessarily UI stuff just fields required etc) + shouldn't be too much as already did that when recently fleshed out models but no doubt missed much + - then full in front end and flow out to back end as required, remove any backend that was a defunct evolutionary path so no cruft left around + - Keep working on front and back responds to front needs as I go + - load and stress test on client + +todo: should webPackCHunkNames be subdivided for service section because some people do quotes might not do service wo etc?? + it's going to be large, maybe it would need breakdown?? Just an idea + + todo: how far to extend down tags, custom fields , wiki because technically could do that easily, each child/grandchild will have own popup edit form to place those controls