devdocs/todo.txt

@@ -5,6 +5,10 @@ Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOiIxNTQ0NTU5NzAwIiwiZXhwIjoi
 
 ## IMMEDIATE ITEMS
 
+Hope the holidays were happy and peaceful and you are energized to work and even if you aren't YOU BETTA WERK!
+
+Need a sprint to get to a fully testable client with entry form, list and as much as possible all features from COMMON-* specs list 
+
 -----------------------
 
 TODO CLIENT STUFF	
@@ -12,10 +16,26 @@ 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
 
-	- TODO: Will need currency symbol, date format, numeric format from user settings at server
-			- rather than try to use local browser settings which is fraught with peril will need to be specified at server itself
-			- Wherever I am currently storing time zone that's where these other settings need to be 
-			- Need to find out in client world what format should be stored and how to document it
+	- LOCALE 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
+
 
 	- 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)
 
@@ -35,12 +55,6 @@ TODO CLIENT STUFF
 	- Need a test user that has access to every possible role so that I can see all the roles for testing purposes
 	- About page has too big of margins on each side of display
 	- numeric inputs need to be set as such so that the number keyboard appears
-
-	- TODO: Will need currency symbol, date format, numeric format from user settings at server
-		- rather than try to use local browser settings which is fraught with peril will need to be specified at server itself
-		- Wherever I am currently storing time zone that's where these other settings need to be 
-	
-
 	- Make the copyright banner at bottom left aligned, right now it seems weird in small iPhone size when it breaks to two lines (make text smaller?)
 	- Change server api page favicon to look like a SERVER version of the AyaNova logo, not the same one as the client uses [ fuck it, why? TTM!]
 	- Disable google fonts for manual / docs generator: