✨ OvO ✨

OvO is a Dart-first schema declaration and validation library.

Introduction

OvO is a Dart-first schema declaration and validation library. We use the technical term "Schema" to define any data type, from simple single data (for example: string/int, etc.) to complex nested Map.

OvO is designed to be as user-friendly and developer-friendly as possible, with the goal of eliminating tedious type checking and object deserialization. It is easy to compose complex data structure validation using simple declaration validation.

several important aspects

• A fun walkthrough of Dart type extensions
• Simple and chained interface calls
• Can be used on any Dart platform (Dart, Web, Flutter)

Sponsors

I am very grateful and encouraged for any level of sponsorship, which will help me continue to develop and maintain this project.

• GitHub Sponsors
• Open collective
• Patreon

Installation

We are more aggressive and use higher versions of Dart stable versions as much as possible.

Install from command line

Install from pubspec.yaml

Basic Usage

Create a simple string schema:

Creating an JSON schema:

Types

OvO provides type validation with dependent type parameters, and also built-in some common types. You can declare a type validation by OvO<T>, where T is a type parameter and can be any type.

Let's try to create a String type validation:

Or, we create a validation of Record type that is not built-in:

Of course, you can also use it to validate a custom class:

Basic type validation depends on the built-in is keyword in Dart, which is fully capable of most type validation. However, if you need more complex type validation, you can use the constructor of OvO<T> to create a custom type validation.

Any

Any type validation can accept a non-null value of any type. It is an alias of OvO<Object>.

Array

Array type validation can accept an iterable value (for example: List, Set, Iterable, etc.). It is not an alias of OvO<Iterable<T>>, but a specific type validation.

Array accepts a parameter of type OvO<T> to validate each element in the array.

.min/.max/.size

.min/.max/.size have the same parameters and type signatures, and they all accept a parameter of type int to validate the length of the array.

• .min validates that the length of the array must be greater than or equal to the specified length.
• .max validates that the length of the array must be less than or equal to the specified length.
• .size validates that the length of the array must be equal to the specified length.

.unique

.unique validates that the elements in the array must be unique, similar to Set in Dart.

Boolean

Boolean type validation can accept a value of type bool. It is an alias of OvO<bool>.

另外，他还有两个额外的扩展方法：

In addition, it has two additional extension methods:

• .isTrue - 验证值必须为 true。

• .isFalse - 验证值必须为 false。

• .isTrue - validates that the value must be true.
• .isFalse - validates that the value must be false.

Of course, you can use OvO<bool> instead of Boolean type validation, but Boolean type validation is more semantic.

Number

Number type validation can accept a value of type num. It is an alias of OvO<num>.

If you need to validate an integer, you can use the Integer type validation, which is an alias of OvO<int>. To validate a floating-point number, you can use the Double type validation, which is an alias of OvO<double>.

Integer and Double are both subtypes of Number:

OvO<num> also contains some additional methods:

String

String type validation can accept a value of type String. It is an alias of OvO<String>.

OvO<String> also contains some additional methods:

Object

Object type validation can accept a value of type Map. It is an implementation of OvO<Map<String, T>>.

Of course, if you just want to simply validate a value of type Map<K, T>, you can use OvO<Map<K, T>> instead of Object type validation.

Functional

.nullable

The .nullable method can convert a type validation to a type validation that accepts null.

.refine

.refine is a method that allows you to customize the validation. It accepts a validation function of FutureOr<bool> Function(T data) to facilitate validation according to the actual situation.

It is worth noting that many of the built-in extension methods are implemented based on the .refine method.

.transform

.transform is a method that allows you to customize the method of converting data types. It works on the principle of Onion Model.

Pre-transformation

Pre-transformation allows you to pre-process the raw data to be parsed, and then hand it over to the next converter, and finally hand it over to the type validator for verification:

Post-transformation

Using the next parameter in the callback, you can perform post-transformation of the data after the type validator is verified successfully:

.withDefault

.withDefault allows a nullable value T? to be replaced with a default value T when the value is null.

As you can see, the .withDefault method will automatically attach the .nullable method, so you don't need to call the .nullable method manually.

Compositions

AnyOf (OR)

AnyOf type validation can accept any of the multiple type validations.

AllOf (AND)

AllOf type validation can accept all types in multiple type validations.

OneOf (XOR)

OneOf type validation can accept one type in multiple type validations. If multiple validations match, an exception is thrown.

Not (NOT)

Not type validation can accept any type validation, but if the specified type validation is matched, an exception is thrown.

Const

Const type validation can accept a constant value.

Using Const we can implement string literals in JSON:

Used in conjunction with conversion, we can implement Enum type validation: