devdocs/todo.txt

@@ -20,7 +20,8 @@ UPDATE SPEC DOCS with new format and names etc or at least remove nonsense as ne
 UPDATE MANUAL API REGARDING LISTS
 
 
-
+CLIENT / TEST ROLE NAME CHANGE 
+	- "client" now "customer"
 
 
 CLIENT PROJECT CUSTOM FIELDS CHANGE
@@ -43,6 +44,12 @@ DO CLIENT STUFF NOW COME BACK TO THIS STUFF LATER
 TODO: the license being logged breaks the format of the log file because it has line breaks etc, so instead, maybe log out as a single line (remove breaks)
 	- Or maybe don't log it at all, what's the point?  People can just edit it, maybe the DBID is the only really useful thing so we can match it for support to the customer
 	- or just log the ID number or a more succint version
+	\
+
+TODO: Need route to gather all object role rights in a format useful to display in UI so that a biz manager can see at a glance the rights for different roles to objects	
+	- This way it's dynamic and picked up from the code itself which is always the source of truth so no need to put in the manual
+	- Would likely want to display multiple ways: for a specific object or role or selected user maybe too in the user info form ("effective roles")
+	- Move this over to client once the backend supports it
 
 *** BEFORE NEXT UPDATE TO DEVOPS SERVER:::::::
 TODO: 2019-06-07 10:47:57.8894|WARN|Microsoft.AspNetCore.Cors.Infrastructure.CorsService|The CORS protocol does not allow specifying a wildcard (any) origin and credentials at the same time. 
@@ -58,6 +65,7 @@ TODO: DO I NOT HAVE AN ERASE DB ROUTE?
 TODO: API RATE LIMITING / THROTTLING
 	- Return code 429 
 	- Going to need rate limiting to save people from themselves 
+	- Have this link from solutions.txt about this: https://github.com/stefanprodan/AspNetCoreRateLimit
 	- All the big api's have hourly limits on requests and also limits on total data throughput per hour 
 	- (minute as well which actually makes more sense since it means they would only be down for a minute if they exceed it) too
 	- Find out what others do