ayanova/devdocs/todo.txt

@@ -229,17 +229,13 @@ CURRENTLY DOING: error and ordering stuff
 
 OVERALL	
 	ORDERING AND ERRORS	
-		- since each graph item is saved one by one, the client knows which one it's sending so the Client should hydrate the correct collection error index
+	- DELETE ISSUE: 
-			server should act like its' a standalone object when reporting errors	
+		because it's removing the row on delete but not deleting until save, any errors can't be displayed correctly
-			this way, no need to modify existing code at all (po etc)
+		TODO: move to a "soft delete" get rid of the deleted items separate array
-		- woitem must show error indicator in row if error is in it's children so user knows where to go
+			- on delete flag an item as "deleted=true"
-		
+			- modify the Items method that provides the array to the table so hide "deleted=true" items 
-	
+			- on save iterate the graph looking for deleted=true and attempt delete
-			`Items[${activeWoItemIndex}].scheduledUsers[
+			- on fail of delete set deleted=true to false so it will show but make sure to do it *IN* the delete method so it's ready for later to show the error
-              ${activeItemIndex}
-            ].estimatedQuantity`
-			Items[3].scheduledUsers[ 0 ].estimatedQuantity 
-			target: "Items[3].scheduledUsers[0].EstimatedQuantity"
 	
 	- test partial save (### and delete ###) with fail at each level (make up a fail if have to at server)
 	- Error messages should display correctly both in alert box and in each item's controls