devdocs/specs/core-list-graph-datatable-filtering-paging.txt

@@ -27,7 +27,7 @@ Filters are saved to the database:
             - op=one of the values specified in the FilterComparisonOperator class in Biz namespace
             - value= straight up direct comparison value
                 - If string then a string fragment, case is sensitive
-                - If date then iso style date
+                - If date then iso style date //RAVEN NOTE: it is my intention that dates come in iso8601 UTC format from the client
                 - could be whole number or decimal number
                 - Could be a special "macro" filter value like "[THIS_MONTH]" (always surrounded by square brackets, no need to disambiguate with a string because only applies to non string values)
                 - Could be a series of id values like this "[23,45,56,123]" as in tag id's or something related to that case.
@@ -59,10 +59,12 @@ NOTES ABOUT WHY I DID THE FILTEROPTIONS LIKE I DID:
 LIST FILTERING TODO
     - DONE test for fetching widget filter options (localized, so have two users test each for expected response)
     - Add test for excercising all of DataFilterController route including rights to non personal alternative owner etc
-Add test for correctly validated Widget datafilter when saved or updated via datafiltercontroller (sanity check of the filter settings and options IFilterableObject implemented)
+    - Add test for correctly validated Widget datafilter when saved or updated via datafiltercontroller (sanity check of the filter settings and options IFilterableObject implemented)
 
 Add test for providing saved filter id to widgetlist and recieving correct filtered / paged / sorted results (test all those)
     - Requires filter to sql code to be written and changes to the widgetlist route
+    - This is where it gets real! Happy monday!! :)
+    - Copy as much from v7 as possible
 
 - Client side
   - Implement filter editor dialog and test