devdocs/specs/core-display-format-template-system.txt

@@ -39,6 +39,10 @@ Server
         - Incurrs more computing ops at the server but bandwidth is more expensive than server power all around
         - Clients could be shitty and slow, this elminates that prospect
         - Easier to code in c# than in javascript! ;)
+    - PICKLISTS and RIGHTS
+        - Initially I had picklist objects with just name and id and anyone could fetch them of any role, however, this isn't right and 
+            - I'm leaving the rights up to the case by case basis and will address it when the client dev drives a requirement for it
+            - I'm thinking if people don't want a field exposed in mini list then don't put it into the template
 
 Back AND front end
     - Need to handle changes in fields gracefully i.e. a new field added in an update, a field removed in an update cleans out the template when detected etc

devdocs/todo.txt

@@ -20,9 +20,7 @@ REALLY MAKING MORE PROGRESS WHEN CLIENT DEV DRIVES BACKEND DEV, STICK TO THAT!!
 -----------------------
 
 GRID LISTS TODO NOW:
-	- Turn PagingOptions object into ListOptions object	
-	- Add list format option ("mini"=true thing) to ListOptions object
-		- It's prescence with mini=true means that the picklist format is returned
+
 	- Combine PickList route and WidgetList route into single "List" route with an internal nameof "WidgetList"
 		- if mini=true then it sends back the two column result templated
 		- Otherwise it sends back the full list (templated)

server/AyaNova/ControllerHelpers/ListOptions.cs

@@ -20,8 +20,12 @@ namespace AyaNova.Api.ControllerHelpers
 
         //Data filter id to use with this list query
         //0 or less means no filter
+        [FromQuery]
         public long DataFilterId { get; set; }
 
+        [FromQuery]
+        public bool Mini { get; set; }
+
 
     }