ayanova/devdocs/todo.txt

@@ -79,18 +79,19 @@ DONE: Widget - NOTES FIELD
 DONE: TAGS!!! 	
 	- Implement and componentize
 
+TODO: Server SEED DATA WIDGET CUSTOM FIELDS DEFINITION 
 TODO: WIDGET Customize menu item
 	- Make a menu item that shows in Widget edit form for users who are BizAdminFull only, title is "customize"
 	- this takes user to customize form where they can customize the widget form, set custom fields, maybe what shows or not etc
 	- this is to customize the form but it should contain a link to the locale text editor in case that's what they actually intend to customize
 TODO: Form customize UI
 	- Where you create custom fields and edit 
+	- If a user changes a field data type there needs to be a big warning before accepting it.
 TODO: Custom fields
-	- DONE Server route that can verify if customization is still valid
-		- Client needs to cache the form customization settings because it would eat up bandwidth to check *every* time that the form is loaded
-		- So need client to keep that cached, and either every time or periodically check with the server to see if it's still valid by sending the known concurrency token to the get customization route
-			- If the concurrency token is still valid it returns the least possible data, perhaps the unchange or not modified http code
-			- If the concurrency token is invalid then it returns the form custom data for that form to replace what is held
+	- Needs to cache the customization data of the form and concurrency token used to fetch it and then it checks the concurrency token periodically
+	- Needs to be aware of and handle the fact that the end user may change the data type 		
+		- if it expects a type of value and finds one it can't co-erce into the new type then it should zap it or set it null by default.
+		- This could get ugly so just stick to a simple system like wiping uncoercable data and fuck it, they made their choice :)
 	- Implement then Componentize
 	- Maybe start with a component first now that I have my feet wet in it, saves time
 	- Have to think about the design, but probably most useful when on the same page as the main record just like in v7 windows
@@ -99,7 +100,10 @@ TODO: Custom fields
 	- Though, these need to be part of the record as well, hmmm...maybe better if they appear to be just normal fields and are added dynamically??
 		- It would be nice though to just insert a slot and let a component handle it rather than buncvh of code on every form...
 		- It's kind of like one control that is bound to the JSON custom fields-field and it would update it as edited and required so I guess this is how to think about it and implement it, as a control
-	
+TODO: Support form customization beyond Custom:
+	- hide fields not used
+	- force user to enter a value in a field optionally that isn't already required
+
 
 TODO: Record history display / check other AyaNova 7 options / buttons that need to carry forward
 	- implement and componentize