ayanova/devdocs/todo.txt

@@ -45,7 +45,13 @@ CURRENT ROADMAP
 CURRENT TODOs
 =-=-=-=-=-=-=
 
-NOW:  working on Custom2 biz rule when empty on regular record (not new yet, just getting it working on regular up front)
+TODO: Custom fields component
+	- implement each type of control
+	- Add code to coerce the value or handle a completely change of datatype on the record
+		- i.e. it was text and now is a date etc
+		
+
+
 	
 TODO: Make sure can easily make new record in Widget form before getting into deeper stuff or making any other object forms.
 
@@ -59,25 +65,6 @@ TODO: Widget edit form, new record sb time and dates pre-filled in? Server invol
 	- some objects may be configurable what the default date/time range is so maybe enable that for widget to test
 	- SB defaults route on server or is this a profile thing and user selectable?
 
-TODO: Widget edit form, new record cdata error as it's empty on new
-	- To see, create new and edit the custom2
-
-TODO: Custom fields
-	- Needs to cache the customization data of the form and concurrency token used to fetch it and then it checks the concurrency token periodically
-		- {"data":{"id":1,"concurrencyToken":3761005,"formKey":"widget","template":"[{\"fld\":\"WidgetNotes\",\"required\":\"true\"},{\"fld\":\"WidgetCustom1\",\"hide\":\"false\",\"required\":\"false\",\"type\":\"datetime\"},{\"fld\":\"WidgetCustom2\",\"hide\":\"false\",\"required\":\"true\",\"type\":\"text\"},{\"fld\":\"WidgetCustom3\",\"hide\":\"false\",\"required\":\"false\",\"type\":\"number\"},{\"fld\":\"WidgetCustom4\",\"hide\":\"false\",\"required\":\"false\",\"type\":\"bool\"},{\"fld\":\"WidgetCustom5\",\"hide\":\"false\",\"required\":\"false\",\"type\":\"currency\"},{\"fld\":\"WidgetCustom6\",\"hide\":\"false\",\"required\":\"false\",\"type\":\"date\"},{\"fld\":\"WidgetCustom7\",\"hide\":\"false\",\"required\":\"false\",\"type\":\"time\"}]"}}
-
-	- 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
-	- Should be a single component I can reference on the form that handles it all directly
-	- Custom field "slot" maybe just like the VUE Way so that it can be easily optionally shown or not in it's slot
-	- 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: 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.