ayanova/devdocs/todo.txt

@@ -14,27 +14,16 @@ TODO CLIENT STUFF
 
 TODO NEXT
 
+End to end action
+	- The faster I get to a fully working basic level like being able to do data entry and submit to server new or updated records, the faster I can flesh out all the rest
+	- Code the submit data to server route for update
+	- Code for new record to the server
 
-GZ VALIDATE 
-	- Add rules for each field type validation
-	- Is there anything pulled into the validate code directly that is already available off the "v" variable?
-		- localization etc
+Simulate server broken rules so can integrate into ui and rule system
 
-Going to need to handle localized numeric entry formats
-
-
-DATETIME
 
 - Validation
-	- after much fuckery it's becoming clear that between the localization requirements and the complexity of server broken rules coming back from the api that I should just use my own validation code
-		- See here: https://vuetifyjs.com/en/components/forms#form
-		- And here: https://vuetifyjs.com/en/components/text-fields#custom-validation
-		- What is needed is a class that returns an array of functions that can be passed to vuetify "rules" property of components
-		On change each rule is called in turn and if one returns false or a string then it's in an error state
 		- I also need to add that it scans and or keeps a collection of broken rules that come back from the server and each component checks a rule that checks in turn for server broken rules in last api call
-		- And my rules object needs to be localized so I guess it should be aware of the locale object and work with it as required 
-			- Should it lazy load error translations?  (In as batchy a way as possible?)
-			- Or, perhaps it's more convenient to cache all possible regular form entry errors since there isn't really that many, perhaps less than a dozen when it comes down to it
 		- My rules object needs to be coded so I can easily specify a collection of rules appropriate to a form field
 			- So, for example let's say I have a date input, if I commonly need one to be required and be after or before another field then I should have a single combined rule of 
 			RequiredAndAfterTarget and this method is aggregates both the required and the After rules into a single collection returned
@@ -46,9 +35,16 @@ DON'T code the user options with the currency symbol etc until after it's all be
 Locale should fetch those settings the first time it sees they are not present so that they are refreshed upon use and are not stored in localstorage
 (or should they be?  anyway, can work that out later)
 
+
+
 Other fields that are locale dependent
 DateTime field next
 
+
+
+
+FIXES REQUIRED
+
 - API get code is incorrectly dealing with expired bearer cert, a 401 is returned and it tries to parse the result as if it succeeded when it really should trigger a login process
 - Time zone offset mismatch warning needs expansion, it should only prompt a few times (maybe or find a way to deal with this) and it should offer to change it at the server automatically
 - Localize time zone mismatch warning
@@ -160,6 +156,10 @@ Make all fields work according to specs below
 			- What to do if they edit?  Refresh the list but keep the same page location?
 
 
+TESTING TODO
+Localized input and parsing and validation
+	- Going to need to handle localized numeric entry formats
+	- Deal with this once form is in good shape and worth testing with different locales
 -----------------
 
 TODO AFTER CLIENT block ABOVE: