ayanova/devdocs/todo.txt

@@ -60,7 +60,7 @@ todo: cleanup unnecessary use of a ayatype access inside the Methods of objects
 todo: use const, not let unless need to reassign the variable
 	Going to need a case by case through all uses but it's a very important precaution so code it that way now for all new code
 
-	
+
 todo: gzdecimal triggering dirty just by clicking into and out of a field witha value in it.
 	also, it sometimes shows without the decimal then with the decimal for editing then without, it's crazy
 	the decimal thing is probbly what's triggering the dirty change.
@@ -226,6 +226,9 @@ todo: many biz objects are not using new PUT methodology
 
 
 CURRENTLY DOING: make from new
+	current issues:
+		setting to locked state does not lock in UI even after save
+		I'm thinking it should lock after save but not before on selection and add to wo
 
 BIG PICTURE STUFF	
 	- ability to create from nothing implement whatever is minimally necessary to get it to work and do full crud test at all layers
@@ -239,6 +242,10 @@ BIG PICTURE STUFF
 
 
 CURRENT ACTIONABLE TODOS
+todo: if islockedatserver is true I am still attempting to support editing, but it's a bit mixed up as the user would need to set the status to an unlocked state as well
+	current plan sucks.  Instead it should be treated entirely as readonly if islocked at server with the sole exception of the state so the user is forced to 
+	set an unlocked status, SAVE, *THEN* then can edit at will.
+	Trying to support both at once would be a mess.
 
 todo: need to add a popup error if attempting to save from locked to locked state and there are other changes that need to be saved 
 	(or let error from server handle it?? Not a first class UI experience though and might be a quite common mistake)