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

@@ -33,11 +33,14 @@ Upon user selecting a filter to use the list query string has the regular paging
     - If list not found then it will return a 404 instead of the list    
     - server loads the filter, generates the sql based on the stored filter, adds the sort by and offset / page, runs the query and then returns the data as json collection to the client
 
+NOTE: determined it would be too much trouble for too little gain to validate that the fields specified in the filter actually exist for that object
 
 
 
 LIST FILTERING TODO
     - DONE test for fetching widget filter options (localized, so have two users test each for expected response)
+Need way to check if fields are valid for the object list in question both from the list Datafilter route and future SQL builder
+
 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)