admin/raven-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2020-05-08 15:18:13 +00:00
parent a9332a852d
commit 71523a8bf1
1 changed files with 8 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
ayanova/devdocs/todo.txt
View File

@@ -71,6 +71,14 @@ CURRENT TODOs
CURRENT ITEM: CURRENT ITEM:
Fix existing integration tests
Add tests as I go while adding all the structure of the workorder and all ops
TBD: Does a labor and other grandchild objects record really have an attachment, wiki, and custom fields?
UI? Will it be a table or a whole form or...??
Do tests for every operation on workorder and structure
(implementing all bits in object as required)
TEST: Proposed workorder structure and routes TEST: Proposed workorder structure and routes
RESULT: Basically they work, now need to INTEGRATION TEST RESULT: Basically they work, now need to INTEGRATION TEST
@@ -79,10 +87,6 @@ test: concurrency exception handling in workorder PUT route
test: biz rules test: biz rules
test: does duplicate workorder return full workorder graph (i.e. does the CopyObject function actually copy the entire object and descendents? Or do I need to iterate it) test: does duplicate workorder return full workorder graph (i.e. does the CopyObject function actually copy the entire object and descendents? Or do I need to iterate it)
TOOD: SHOULD I CODE ALL THE ROUTES AND OPS and descendents FOR WORKORDER NOW?
There will be so much to fill in later, maybe while it's fresh in my brain is best time to do it
Does a labor and other grandchild objects record really have an attachment, wiki, and custom fields?
UI? Will it be a table or a whole form or...??
update: v8Export to use new routes for workorder properly update: v8Export to use new routes for workorder properly