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

@@ -25,6 +25,7 @@ Filters are saved to the database:
                 - Could be compound for joins like "table.name" (no a prepends the table name)
                 - Special indirect values such as "[TAGS]" which means cross filter with tags
             - op=one of the values specified in the FilterComparisonOperator class in Biz namespace
+                - Note: no Like on purpose, that would require input, better to hard code a starts with, ends with, contains and not bothering with the negative of those three as I don't see it being widely used
             - value = string version of direct comparison value or could be a special token meaning more
                 - Never an empty string, empty string is invalid value
                 - All Tokens are a value surrounded by this fragment: "{[XXX]}" where XXX is the token
@@ -53,6 +54,7 @@ NOTES ABOUT WHY I DID THE FILTEROPTIONS LIKE I DID:
     //      - Again, a static list of items to check against
 
 
+
     //Where to store that?
     //all cases are via list class so really the whole thing is self contained and no need for an interface at all
 --------------------------------------------------