FoolProof.Core 2.1.0

Starting from the migration to asp.net core of the MVC Foolproof Validation library.

Validation attributes at your disposal.

Validators to compare with other property:

• Is (base class)
• EqualTo
• NotEqualTo
• GreaterThan
• LessThan
• GreaterThanOrEqualTo
• LessThanOrEqualTo
• In (field must be in dependant)
• NotIn (field must not be in dependant)

Validators to compare with specific values:

• Is<T> (base class)
• EqualTo<T>
• NotEqualTo<T>
• GreaterThan<T>
• LessThan<T>
• GreaterThanOrEqualTo<T>
• LessThanOrEqualTo<T>
• In<T>
• NotIn<T>
• IsEmpty
• IsTrue
• IsFalse

Improved required validators:

• RequiredIf (field required if dependant satisfy condition)
• RequiredIfNot (field required if dependant doesn't satisfy condition)
• RequiredIfTrue (field required if dependant value is true)
• RequiredIfFalse (field required if dependant value is false)
• RequiredIfEmpty (field required if dependant has no value)
• RequiredIfNotEmpty (field required if dependant has value)
• RequiredIfRegExMatch (field required if dependant match regex)
• RequiredIfNotRegExMatch (field required if dependant doesn't match regex)
• RegularExpressionIf (field must match regex if dependant satisfy condition)

Predicate validators: Predicate validators will allow you to create complex validation rules (logical predicates), combining other validators (inlcuding the predicate ones).

• Predicate (base abstract class)
• Not(operand)
• And(operand1, operand2,..., operandN)
• Or(operand1, operand2,..., operandN)
• IsValid(property, operand)

operand could be any ValidationAttribute, inlcuding the predicate ones, so you can recursively combine validators to build any logical predicate.

IsValid will let you validate any property in the model, using any existing ValidationAttribute; so combining the predicate validators and the IsValid validator, you can create validation rules to be evaluated at the model level (aka model-wise validation).

Client-side validation

All the validators are available for client side validation. Although you can combine any ValidationAttribute using the predicate validators, only the ValidationAttribute with a registered IAttributeAdapter will be available for client-side validation; of course, this includes all the validator provided by this library (and many others from System.ComponentModel.DataAnnotations).

This library provides you with an HTML helper method ModelValidation to render the model-wise validation as you would do with any property validation. To bring this helper in context, you need to include the FoolProof.Core namespace with the @using directive. Take a look at the predicate page in the example app.

Installation

NuGet: install-package FoolProof.Core

Setting Up

• Include namespace FoolProof.Core
• Just add this line services.AddFoolProof(); to your ConfigureServices method on the Startup class; this will register a new IValidationAttributeAdapterProvider.

Example WebApp

You can review a kind of DEMO app (the WebApp used to execute the E2E tests) here: E2E/Demo WebApp