LightVx 2.0.4

There is a newer version of this package available.
See the version list below for details.
dotnet add package LightVx --version 2.0.4
NuGet\Install-Package LightVx -Version 2.0.4
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="LightVx" Version="2.0.4" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add LightVx --version 2.0.4
#r "nuget: LightVx, 2.0.4"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install LightVx as a Cake Addin
#addin nuget:?package=LightVx&version=2.0.4

// Install LightVx as a Cake Tool
#tool nuget:?package=LightVx&version=2.0.4

Light Vx

LightVx is a light, easy and extensible validation framework for .Net which includes a Fluent API.
It's intended to help validating user input in apps, or service requests in Web Services or Web API's, or anywhere you need to validate data.

Author

Tim Wheeler - http://blog.timwheeler.io/ Contact - http://timwheeler.io/#contact

Download

Source on GitHub Nuget Package

Built-in Validators

  • Aggregate - Combines other validators
  • AlphaNumeric - Alphabetical or Numbers
  • AlphaNumericHyphen - Alphabetical, Numbers, Hyphens and Spaces
  • AlphaText - a to Z and spaces
  • Decimal - a decimal value
  • Email - email address
  • Url - Uri/Url
  • Empty - will match an empty string
  • HexColor - a valid hex color
  • IsNull - matches null
  • Length - matches string length. Supply min and max value.
  • MaxLength - matches a max string length
  • MinLength - matches a min string length
  • Max - validates a number is not greater than x. If input is an Array or ICollection then it will validate against number of items.
  • Min - validates a number is not less than x. If input is an Array or ICollection then it will validate against number of items.
  • NotEmpty - must not be empty string
  • Numeric - numbers only
  • PhoneAndLength - combine phone number validator and length validator
  • PhoneNumber - attempts to validate a phone number with optional braces
  • SqlSafeText - Detects use of characters used in SQL Injection Attacks
  • XssSafeText - Detects use of characters used in XSS Attacks
  • SafeText - Combines both the XSS and SQL validators.
  • Url - validates against a valid url
  • MinDate - Date is equal to or greater than
  • MaxDate - Date is equal to or less than
  • SqlSafeDateValidator - Checks if a datetime or datetime? is within the valid SQL date range
  • InCollectionValidator - Checks if the input is an item within an ICollection.
  • ContainsValidator - Checks to ensure the specified content exists within the input
  • NotContainsValidator - Checks to ensure the specified content does not exist within the input

Object Validation Feature

Recently, this framework has been upgraded to provide a more holistic approach to validating an object. Object Validation works by creating your own validation class to define all the validators. The following example validates the Name and Date of Birth properties of the Customer.

public class CustomerValidator : ObjectValidator<Customer>
    {
        public CustomerValidator(Customer customer) : base(customer)
        {
            Eval(Input.Name, "Name")
                .IsNotEmpty()
                .HasMinLength(3)
                .HasMaxLength(120)
                .IsNameText(); //Allows alpha, hyphen, space, apostrophie

            Eval(Input.DOB, "Date of Birth")
                .IsNotNull()
                .IsBefore(DateTime.Now);
        }
    }

Accessing the validator is similiar to all other validators, but note that the ObjectValidator does not implement IValidator. Instead it implements 'IObjectValidator<T>'. Here is an example based on calling the above CustomerValidator:

	var customer = new Customer();
    customer.Name = "Joe Someone";
    customer.DOB = DateTime.Now.AddYears(-25);

    var validator = new CustomerValidator(customer);
	Assert.IsTrue(validator.IsValid, $"Failed to validate: {validator.ToString()}" );

Location Specific Validators

US - United States

Note: To use the US Validators in the Fluent API add use namespace: LightVx.Validators.US

  • USStateValidator - Checks values against a known list of US state codes (2 characters uppercase)

Fluent API

Using the Validator.Eval method you can call a number of validators.
Example

            var input = "123ABC";
            Validator.Eval(input, "Customer ID")
                .Required()
                .IsAlphaNumeric()
                .HasLength(6, 6)
                .Success((() =>
                {
                    Console.WriteLine("Validation succeeded");
                }))
                .Fail((errors, validators) =>
                {
                    Console.WriteLine(string.Join(",", errors));
                    // Validation failed, put your failure logic here
                });

For more examples, see below.

Available Methods

  • Required() - must not be null or empty string

  • HasLength(int min, int? max)

  • IsAlphaNumeric()

  • IsAlphaText()

  • IsDecimal()

  • IsEmailAddress()

  • IsNumeric()

  • IsPhoneNumber()

  • IsSafeText()

  • IsSafeForSql()

  • IsSafeForXss()

  • IsUrl()

  • Min(int value)

  • Min(double value)

  • Min(decimal value)

  • Max(int/double/decimal/date value)

  • IsEmpty()

  • IsNotEmpty()

  • IsNull()

  • IsNotNull()

  • HasMinLength(int minLength)

  • HasMaxLength(int maxLength)

  • IsAfter(DateTime date)

  • IsBefore(DateTime date)

  • IsAfter(DateTime date)

  • IsBetween(DateTime startDate, DateTime endDate)

  • IsSqlDate()

  • IsIn(ICollection items, bool ignoreCase = false)

  • DoesNotTraverse()

  • Contains(string content, bool ignoreCase = false)

  • DoesNotContain(string content, bool ignoreCase = false) US Validation Extensions

  • IsUSState() - Checks values against a known list of US state codes (2 characters uppercase)

Fluent API Examples

Example using Result

            var input = 100; //user input to be validated
            var result = Validator.Eval(input, "Quantity Requested")
                .Required()
                .Min(50)
                .Max(100);
            if (result.IsValid == false)
            {
                Console.WriteLine(string.Join(";", result.ErrorMessages));
                //... add failure logic here
            }

Inline Example

            var input = "https://github.com/TjWheeler/LightVx"; //user input to be validated
            Validator.Eval(input, "Source Url")
                .Required()
                .IsUrl()
                .Success((() =>
                {
                    Console.WriteLine("Validation succeeded");
                }))
                .Fail((errors, validators) =>
                {
                    Console.WriteLine(string.Join(",", errors));
                    // Validation failed, put your failure logic here
                });

Examples using Validation Helper

            //WebApi - Validate that the text is matches Alphabet only
            var input = "ABC";
            string errorMessage;
            if (Validator.IsNotValid<AlphaTextValidator>(input, "First Name" , out errorMessage))
            {
                return BadRequest($"The input is invalid: {errorMessage}");
            }

Examples using Validators directly

Note: Although you can call the validators directly, using the Validation helper is more convenient.

            //Validate numberic
            string input = "123ABC";
            IValidator validator = new NumericValidator();
            validator.Validate(input, "My Field Name");
            if (!validator.IsValid)
            {
                Console.WriteLine("Input: " + input + " return error (" + validator.ErrorMessage + ")");
            }

Extending and creating your own validators

In the following example, we are inheriting from an AggregateValidator, this allows us to combine validators.

Creating a Post Code Validator by combining other validators.

//Step 1: Add the custom validator
public class PostCodeValidator : AggregatedValidator
    {
        public PostCodeValidator()
        {
            AddValidator(new LengthValidator(4, 4));
            AddValidator(new NumericValidator());
        }
    }

//Step 2: Add an extension method
public static class PostCodeValidatorExtension
    {
        public static ValidatorFluent IsPostCode(this ValidatorFluent fluentApi)
        {
            fluentApi.AddValidator(new PostCodeValidator());
            return fluentApi;
        }
    }

//Step 3: Call it to validate input

    public void ExampleCustomValidator()
    {
        string input = "...";
        var isValid = Validator.Eval(input, "MyFieldName")
            .Required()
            .IsPostCode()
            .Fail(((errors, validators) =>
            {
                Console.WriteLine("Example failure: " + string.Join(";", errors));
            })).IsValid;
    }

Creating your own validator

Create a class and inherit ValidatorBase. The only method you need to implement is Validate. There are some base methods that will make it easy to validate using Regular Expressions. Here's an example of one of the built in validators.

    /// <summary>
    ///     Validate Email Addresses
    /// </summary>
    public class EmailValidator : ValidatorBase
    {
        protected override string Expression => @"^([\&\w-\.]+)@((\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.)|(([\w-]+\.)+))([a-zA-Z]{2,4}|[0-9]{1,3})(\]?)$";

        protected override void Validate()
        {
            if (_Input == null || (string) _Input == string.Empty)
            {
                Succeed();
                return;
            }

            if (SingleMatch((string) _Input))
                Succeed();
            else
                Fail("is not a valid email address.");
        }
    }

When using Regular expressions you can also use the HasMatch and MatchCount base methods.

Product 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.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net40 is compatible.  net403 was computed.  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. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.
  • .NETFramework 4.0

    • No dependencies.
  • .NETFramework 4.5

    • No dependencies.
  • .NETStandard 2.0

    • No dependencies.

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
4.0.1 2,063 4/20/2023
4.0.0 318 2/10/2023
3.1.0 336 1/21/2023
3.0.3 296 1/21/2023
3.0.2 279 1/20/2023
3.0.1 7,837 7/24/2022
3.0.0 432 7/24/2022
2.0.8 427 7/23/2022
2.0.7 455 7/13/2022
2.0.6 449 6/19/2022
2.0.5 490 4/27/2022
2.0.4 428 4/15/2022
2.0.3 569 11/16/2020
2.0.2 663 5/28/2020
2.0.1 478 5/22/2020
2.0.0 492 4/21/2020
1.2.0 1,717 5/4/2018
1.1.1 1,014 4/27/2018
1.1.0 1,103 3/8/2018
1.0.3 889 2/20/2018
1.0.2 1,077 2/12/2018
1.0.1 972 2/11/2018
1.0.0 962 2/11/2018