LambdaExpressionBuilder-PR
1.2.2.1
dotnet add package LambdaExpressionBuilder-PR --version 1.2.2.1
NuGet\Install-Package LambdaExpressionBuilder-PR -Version 1.2.2.1
<PackageReference Include="LambdaExpressionBuilder-PR" Version="1.2.2.1" />
paket add LambdaExpressionBuilder-PR --version 1.2.2.1
#r "nuget: LambdaExpressionBuilder-PR, 1.2.2.1"
// Install LambdaExpressionBuilder-PR as a Cake Addin #addin nuget:?package=LambdaExpressionBuilder-PR&version=1.2.2.1 // Install LambdaExpressionBuilder-PR as a Cake Tool #tool nuget:?package=LambdaExpressionBuilder-PR&version=1.2.2.1
Lambda Expression Builder
This is not a replacement of LambdaExpressionBuilder. I've just built on top of it; made changes and improvements (in my opinion)
Are you looking for a library that can build lambda expressions easily? Use the Lambda Expression Builder to easily build a filter that you can apply to lists and database queries. You can even use this as a base to allow you to build filters dynamically.
Packed with features; you can save and re-run filters, not have to worry about NULL
checks (it's automatic), build complex queries with groups and more!
Features:
- Ability to reference properties by their names
- Ability to reference properties from a property
- Ability to reference properties from list items
- Built-in null-checks
- Built-in XML serialization
- Globalization support
- Group expressions for more complex scenarios
- Match a list of values (i.e. A first name that matches any of: "John", "Jess")
What's New: Version 1.2.2
- Added a shorthand function for operations that require no values (i.e.
Operation.IsNull
) - Added method to fetch the correct
MatchType
, when default is provided - More bug fixes. When one is solved another is found
Release Notes About Version 1.2.1
PLEASE NOTE THIS IS A BREAKING CHANGE I have left this in due to the updates being only a day apart
- Simplified enumerables - To make it easier to type, and easier to read, I have simplified 2 enums. This is the "breaking change" I was refering to.
- Operations & default match-types - Operations now have a default MatchType. This is the match-type that will be called by default.
- Bug fixes and other minor improvements
For a full list of changes and previous revisions, see the Change Log
Suggestions & Issues
Feel free to leave comments, and to place issues, if you find errors or realise there is any missing feature.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net45 is compatible. net451 was computed. net452 was computed. net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
-
- Microsoft.Net.Compilers (>= 1.0.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
1.2.2.1 | 1,089 | 7/13/2018 |
1.2.2 | 938 | 3/26/2018 |
1.2.0 | 1,096 | 1/22/2018 |
1.2.0-beta-01 | 838 | 1/19/2018 |
PLEASE PREP FOR NEW ENUM NAMES
Two operation "type name"'s have been changed. "FilterStatementConnector" is now "Connector". "FilterStatementMatchType" is now "MatchType".