Now you can query your endpoint with the DynamicFilter properties. Check "tests" folder on the Api projects for examples.

DynamicFilter.Parser will transform your URI Queries into .Net Expressions. That way, you can use these expressions to filter your values into your database repository.

Simple Filter

You can use a DynamicComplexModel model for filtering. A DynamicFilterModel model without additional properties is also available.

Example Uri:

Expression generated by Uri:

Filters are also supported for nested collections.

Your request will be converted to:

If the standard behavior for arrays and lists using the Any method does not suit you, you can add the '=' sign after the comparison operator, after which the system will use the All method for arrays:

Your request will be converted to:

The parser supports the count property for the collection, you can use it as a regular collection property:

If you need to filter values by default for the value type, use \default:

Complex Filter

Boolean operators &&(and) and ||(or) are supported.

Example Uri:

Since version 2.0 more complex filters are available. You can use brackets to create more complex expressions.

You can nest multiple parentheses to create complex expressions.

Attention!

For correct parsing of the filter, when using brackets, enclose all logical elements in brackets, for example:

Not correct

Correct (age>=27 in brackets)

Nested Filer

Example Uri:

Expression generated by Uri:

Ordering

You can also order your queries via DynamicFilter. You simply need to add an order parameter on your query, where you specify the property you'll use for order.

Default order type is Ascending. You can adding a - before the name switches to sorting descendingly..

To sort by multiple properties:

If you do not specify the sort type, asc is used by default.

On your DynamicFilter object received on the endpoint, you'll get the orderType as an Enum, this way you can order by the type specified on enum.

Pagging

In romaklayt.DynamicFilter.Extensions.* there is a method of expanding the ToPageModel which returns PageModel with info about page and your filtered data.

The PageModel is built on top of the List<T> so to add page information to the server response you need to add an AddPageInfoFilter which will write the page information to the headers.

If you no need page info, you simply needs to add the parameters page and pagesize on your get request.

If you specify the page number and size in the filter model, pagination is disabled when using ApplyFilter. You can also disable pagination by forcibly calling:

Example:

Select

To select, you simply needs to add the parameter select with the properties you want to select from. It will render either an linq select and a plain string select.

If you select a nested property, from default, the properties from the root model will be ignored, to select all the root properties, use the word root.

If you need to select properties from only one model (the GetById method, for example), you can also use the method ** ApplyFilter**.

Filter operator support

All operators support negation, you need to put "!" before the operator (e.g. !== for Equals)