devdocs/todo.txt

@@ -12,28 +12,30 @@ Need a sprint to get to a fully testable client with entry form, list and as muc
 ///
 TODO CLIENT STUFF	
 
-	- Validate time zone offset is accurate: it should validate the time zone offset when the client software starts and if it's found to be off what was set offer to change it automatically
-		- This way it works client to client and will handle DST changes almost automatically
+	- Client: initialize after login sets locale formats for everything.
+		- First it gets useroptions to know what to override or not, then sets defaults based on browser or override settings in central client area for all display/parsing etc
 
-	- LOCALE USEROPTIONS SETTINGS NEEDED:
+	- SERVER CHANGE: USEROPTIONS SETTINGS NEEDED:
 		- Will need currency symbol, date format, numeric format from user settings at server
 
 			- Allow a choice: browser native display format or forced format set in useroptions
 			- Code the client so it will do either one from a setting fetched off the server for a session			
 			
-			- USE BROWSER or OVERRIDE
-				- Need a user browser native format for displaying dates and times and numbers
-				- Or user can override with the below
-			- NUMERIC FIELDS NEEDED
-				- Digit grouping symbol, i.e. the , in 1,000,000
-				- Decimal symbol, i.e. the . in 1.00
-				- Currency symbol string (may be more than one character in some locales i.e. "Eur")
-				- Negative display format one of these: -1.1, (1.1), 1.1-
-				- Could potentially be one string, i.e. '$0,0.00' which tells us everything we need to know to display any number
-					- No, this makes sense at one level but not at another
-			- DATE / TIME 
-				- Take from day.js (https://github.com/iamkun/dayjs/blob/master/docs/en/API-reference.md#list-of-all-available-formats)
-				- Do not allow anything other than numeric display, i.e. no January or Saturday so we avoid localization issues
+			- THESE SETTINGS NEEDED FOR USEROPTIONS
+				- Use browser TimeZone
+				- Use this timezoneoffset (already have this)
+				- Use browser Numeric format
+				- Override browser with these numeric format settings instead (see below)
+					- Digit grouping symbol i.e. the , in 1,000,000
+					- Decimal symbol i.e. the . in 1.00
+					- Currency symbol string (may be more than one character in some locales i.e. "Eur")
+					- negative display format one of these: -1.1, (1.1), 1.1-
+				- Use browser Datetime format					
+				- Override browser datetime with these settings instead (see below)
+					- One single date format string?  Or one for time, one for date and one for date/time? (see v7)
+						- Take from day.js (https://github.com/iamkun/dayjs/blob/master/docs/en/API-reference.md#list-of-all-available-formats)
+						- Do not allow anything other than numeric display, i.e. no January or Saturday so we avoid localization issues
+
 
 
 	- Error messages: ensure error messages that come back from API that start with LT: will be localized correctly before display / logging (may need string interpolation too for some in future, consider that)

server/AyaNova/Startup.cs

@@ -380,7 +380,7 @@ namespace AyaNova
             // ******************** TESTING WIPE DB *****************************
             //
             //Set this to true to wipe the db and reinstall a trial license and re-seed the data
-            var TESTING_REFRESH_DB = true;//#############################################################################################
+            var TESTING_REFRESH_DB = true;//#######################################################################################
 
 #if (DEBUG)
             //TESTING