ayanova/devdocs/todo.txt

@@ -72,66 +72,16 @@ CURRENT TODOs
 CURRENT ITEM:
 
 
-
-
-
-STATUS - have just made the routes and biz code for wo, woitem, labor, parts.  Make the tests for that then come back and add in the rest of the objects such as I know it
-MAKE THESE INTEGRATION TESTS FTW!
-test: add rest of well known workorder objects then add them to the integration test 
-	WorkOrderItemPartRequests
-	WorkrderItemScheduledUsers
-	WorkorderItemMiscExpenses  <----renamed to Expense not MiscExpense
-	WorkorderItemTravels
-	WorkorderItemTasks
-	WorkorderItemLoans
-	WorkorderItemUnits (new for RAVEN)
-	
-
-
-
-
 update: v8Export to use new routes for workorder properly
+
 TEST EXPORT BIG DATABASE WITH TONS OF ATTACHMENTS
 Finish off the v8 test export then get the below shit done so can move to stage 3 ASAP
 
-  ============================
+
 
 todo: Release AyaNova 7.x (bump version numbers)
 
-
-
-		TEST
-			Do a practical test of a mocked wo, woitem, woitemlabor or whatever, see how it would be updated, fetched concurrency checking etc
-			QUESTIONS:
-				How to do CRUD efficiently with a workorder and client?
-			
-				
-				PROPOSAL TO TEST: 
-					Create enough of a graph to test, 3 layers two grandhild collections should be sufficient:
-						WO
-							WOITEMS
-								WOITEMLABORS
-								WOITEMPARTS
-
-				CREATE (POST):
-					CreateFromxxxx routes (NO TEST REQUIRED)
-					POST accepts NEW workorder full graph (test)
-				RETRIEVE (GET):
-					Get(id) - simple get, just confirm entire graph comes across
-					GetByRelative(ayatype, id) (no test required)
-
-				UPDATE (PUT?)
-					Test code tons of routes method detailed above
-
-					SERVER
-						Server accepts graph at single WO POST route (since it's not a put)
-					UI
-						ui manufactures the return object with the OP fields by doing dirty tracking on changes
-				DELETE
-					Not much here except handling delete will be more intensive and sophisticated when have real data but for now if the graph deletes then that's enough
-					Test how to delete graph without ref. integrity errors
-
-
+	
 	
 
 ---------------------------------------------