Filtering
Gridify supports the following filtering operators:
Conditional Operators
Name | Operator | Usage example |
---|---|---|
Equal | = | "FieldName = Value" |
NotEqual | != | "FieldName !=Value" |
LessThan | < | "FieldName < Value" |
GreaterThan | > | "FieldName > Value" |
GreaterThanOrEqual | >= | "FieldName >=Value" |
LessThanOrEqual | <= | "FieldName <=Value" |
Contains - Like | =* | "FieldName =*Value" |
NotContains - NotLike | !* | "FieldName !*Value" |
StartsWith | ^ | "FieldName ^ Value" |
NotStartsWith | !^ | "FieldName !^ Value" |
EndsWith | $ | "FieldName $ Value" |
NotEndsWith | !$ | "FieldName !$ Value" |
TIP
If you don't specify any value after =
or !=
operators, Gridify search for the default
and null
values.
var x = personsRepo.ApplyFiltering("name=");
this is equivalent to the bellow LINQ query:
var x = personsRepo.Where(p =>
p.Name is null ||
p.Name == string.Empty );
Special Operators
Logical Operators
Using logical operators we easily can create complex queries.
Name | Operator | Usage example |
---|---|---|
AND | , | "FirstName = Value, LastName = Value2" |
OR | | | "FirstName=Value|LastName=Value2" |
Parenthesis | () | "(FirstName=*Jo,Age<30)|(FirstName!=Hn,Age>30)" |
Case Insensitive Operator - /i
The '/i' operator can be use after string values for case insensitive searches. You should only use this operator after the search value.
Example:
var x = personsRepo.ApplyFiltering("FirstName=John/i");
this query matches with JOHN - john - John - jOHn ...
Escaping
Gridify have five special operators , | ( ) /i
to handle complex queries and case-insensitive searches. If you want to use these characters in your query values (after conditional operator), you should add a backslash \
before them. having this regex could be helpful ([(),|]|\/i)
.
JavaScript escape example:
let esc = (v) => v.replace(/([(),|\\]|\/i)/g, '\\$1')
Csharp escape example:
var value = "(test,test2)";
var esc = Regex.Replace(value, "([(),|\\]|\/i)", "\\$1" );
// esc = \(test\,test2\)
Using Indexers
Starting from version v2.15.0
, Gridify supports filtering on any property that is indexable, including sub-collections, arrays, and dictionaries. This feature allows you to create dynamic and flexible queries for a wide range of data structures.
Passing Index/Key to Sub-Collections, Arrays, and Dictionaries
Gridify enables filtering on elements of sub-collections, arrays, and dictionary properties by specifying the index or key within square brackets [ ]
.
Here’s an example:
var gm = new GridifyMapper<TargetType>()
.AddMap("arrayProp", (target, index) => target.MyArray[index].Prop)
.AddMap("dictProp", (target, key) => target.MyDictionary[key]);
var gq = new GridifyQuery
{
Filter = "arrayProp[8] > 10, dictProp[name] = John"
};
In this example:
arrayProp[8] > 10
filters on the 8th element of an array property. dictProp[name] = John
filters on the value associated with the name key in a dictionary property.
This new capability makes Gridify a versatile and robust tool for handling complex data structures in your filtering logic.
Check out Defining Mappings for Indexable Properties for more information.
Custom Operators
Sometimes the default Gridify operators are not enough, For example, if you need an operator for regex matching or when you are using the EntityFramework, you may want to use EF.Functions.FreeText
rather than a LIKE with wildcards. In this case, you can define your own operators. (added in v2.6.0
)
To define a custom operator, you need to create a class that implements the IGridifyOperator
interface. then you need to register it through the global CustomOperators configuration.
TIP
Custom operators must be start with the #
character.
- FreeTextOperator Example:
class FreeTextOperator : IGridifyOperator
{
public string GetOperator() => "#=";
public Expression<OperatorParameter> OperatorHandler()
{
return (prop, value) => EF.Functions.FreeText(prop, value.ToString());
}
}
- RegexMatchOperator Example:
class RegexMatchOperator : IGridifyOperator
{
public string GetOperator() => "#%";
public Expression<OperatorParameter> OperatorHandler()
{
return (prop, value) => Regex.IsMatch(prop.ToString(), value.ToString());
}
}
- InOperator Example:
class InOperator: IGridifyOperator
{
public string GetOperator()
{
return "#In";
}
public Expression<OperatorParameter> OperatorHandler()
{
return (prop, value) => value.ToString()
.Split(";",StringSplitOptions.RemoveEmptyEntries)
.Contains(prop.ToString());
}
}
// usage: .ApplyFiltering("name #In John;David;Felipe")
Registration Example:
GridifyGlobalConfiguration.CustomOperators.Register<FreeTextOperator>();
GridifyGlobalConfiguration.CustomOperators.Register<RegexMatchOperator>();
GridifyGlobalConfiguration.CustomOperators.Register<InOperator>();