ayanova/src/components/work-order-items.vue

@@ -97,6 +97,8 @@
 ////////////////////////////////////////////////////////////////////////////////////////////////////////////
 import GzWoItemScheduledUsers from "../components/work-order-item-scheduled-users.vue";
 /*
+
+todo: delete at shell must walk graph backwards where save would be forwards so delete break out into separate methods called first
     todo: stop using parent vm directly to control state in graph and instead pass down values via props to children and pass up values to parent via events
       https://www.smashingmagazine.com/2020/01/data-components-vue-js/
   
@@ -113,6 +115,7 @@ import GzWoItemScheduledUsers from "../components/work-order-item-scheduled-user
       todo: failed saved on a grandchild item shouldn't preclude the rest saving
         e.g. if there is a concurrency error on a child that shouldn't block the rest but a fatal error probably should
       todo: do we need a dirty indicator at every level??
+      todo: "delete selected item" text instead of "Delete" for subitems
 */
 export default {
   components: {