EDennis.NetCore.LinqTools
1.2.0
See the version list below for details.
dotnet add package EDennis.NetCore.LinqTools --version 1.2.0
NuGet\Install-Package EDennis.NetCore.LinqTools -Version 1.2.0
<PackageReference Include="EDennis.NetCore.LinqTools" Version="1.2.0" />
paket add EDennis.NetCore.LinqTools --version 1.2.0
#r "nuget: EDennis.NetCore.LinqTools, 1.2.0"
// Install EDennis.NetCore.LinqTools as a Cake Addin #addin nuget:?package=EDennis.NetCore.LinqTools&version=1.2.0 // Install EDennis.NetCore.LinqTools as a Cake Tool #tool nuget:?package=EDennis.NetCore.LinqTools&version=1.2.0
EDennis.NetCore.LinqTools
Dynamically applies filtering, sorting, and paging to IEnumerable, IQueryable, and DbSet objects using a JSON-friendly spec.
The Filtering/Sorting/Paging Spec
The specification for filtering, sorting, and paging is represented by a simple, JSON-friendly hierarchical structure.
Example Specification as JSON
{
filter:
[
[
{
property: "Name",
operation: "Eq",
stringValue: "AliceBlue"
}
],
[
{
property: "Red",
operation: "Eq",
stringValue: "0"
},
{
property: "Blue",
operation: "Eq",
stringValue: "0"
}
]
],
sort:
[
{
property: "Red",
direction: "Ascending"
},
{
property: "Green",
direction: "Ascending"
}
],
page:
{
pageNumber: 2,
pageSize: 3
}
}
Filtering Spec
The filtering specification is a two-dimensional array of objects, which can be interpreted as a filter table. Each row in the filter table (an outer array element) represents an intersection (AND-ed) over one or more expression units. Each expression unit consists of a property name, and operation, and a literal value (as a string). Currently supported operations are: Eq, Lt, Le, Gt, Ge, Contains, StartsWith, and EndsWith. All filter rows are unioned (OR-ed) to provide the complete filter. This is analogous to the filtering table in the design mode of a Microsoft Access query.
In the above example, we select all objects where Name = "AliceBlue" or where both Red and Blue properties were equal to zero.
Sorting Spec
The sorting specification is a one-dimensional array of objects, where each object provides a property name and sort direction.
In the above example, we sort by Red (ascending) and then by Green (ascending)
Paging Spec
The paging specification is a single object consisting of a page number and page size.
In the above example, we return the second page, where each page holds three objects.
Other Examples
The test project in this solution includes other examples of filtering, sorting, and paging.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp2.2 is compatible. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
-
.NETCoreApp 2.2
- Microsoft.EntityFrameworkCore (>= 2.2.4)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Added out parameter "pageCount" to FilterSortPage ApplyTo methods