go-ozzo/ozzo-validation

Features

• Go Data Validation - Provides a programmable framework to verify that Go structs and maps meet specific business requirements.
• Field Validation - Checks specified fields of a struct pointer against rules and returns a collection of failures.
• Structural Data Validators - Evaluates the fields of Go structs and maps against a defined set of rules for structural correctness.
• Context Propagation - Propagates a request-scoped context object through the validation chain to rules requiring external state.
• Go Validation Libraries - Implements a declarative, rule-based approach for validating Go structs, maps, and primitive types.
• Context-Aware Validation Engines - Supports propagation of request-scoped context to validation rules, allowing checks to depend on external state.
• Context-Aware Validation - Implements a validation engine that propagates request-scoped context to rules for state-dependent verification.
• Dynamic Validation Rules - Performs runtime validation checks that depend on external request-scoped context values.
• Custom Validation Rules - Enables the creation of new validation logic by implementing a rule interface or wrapping functions.
• Nested Object Validation - Recursively validates nested types that implement a validatable interface to verify embedded fields.
• Recursive Object Validation - Uses Go interfaces to recursively traverse and validate nested data structures and custom types.
• Interface-Driven Validation - Utilizes a common interface to allow custom functions to be wrapped as reusable validation rules.
• Programmable Validation Frameworks - Provides a programmable API for defining validation rules and custom error messages without relying on struct tags.
• Recursive Validation Engines - Features a recursive engine that validates nested structures by calling validation methods on embedded types.
• Recursive Structure Validations - Provides recursive validation for nested structs, maps, and slices to maintain integrity across complex object trees.
• Input Validation - Supplies a set of rules for checking required fields, formats, and allowed values in user-provided data.
• Conditional Validation Rules - Executes specific validation rules only when a boolean condition is met.
• Validation Skipping - Allows bypassing specific validation rules based on a boolean condition or a trigger.
• Range Length Validations - Implements validation for strings, slices, and maps to ensure their length falls within specified ranges.
• Unicode Length Validations - Verifies the number of Unicode code points in a string to ensure length requirements.
• Field Value Placeholders - Provides the ability to inject actual field values into error messages via dynamic placeholders.
• Rule Wrappers - Transforms simple boolean functions into complex validation objects that support custom error messages and metadata.
• Element-Level Validation - Executes a set of validation rules against every individual element within a slice, array, or map.
• Localized Error Messages - Provides the ability to override default failure text with localized error messages for different languages.
• Validation Error Aggregators - Aggregates multiple validation failures into a keyed map associating fields with their specific error messages.
• Forbidden Value Validations - Checks if a value exists within a specified set of forbidden values and returns an error.
• Interface-Based Custom Logic - Defines a custom rule by implementing a specific interface to handle specialized business logic.
• Range Constraints - Checks if numeric values and timestamps fall within specified minimum or maximum thresholds.
• Regular Expression Validations - Verifies if a value matches a specified regular expression pattern and returns an error on failure.
• Request Validation - Offers structured error aggregation into keyed maps suitable for consistent JSON API response failures.
• Allowed Value Validations - Checks if a value is present within a specified set of allowed options.
• Single Value Validators - Checks a single primitive value against a sequence of rules and returns the first error.
• Date Validation - Verifies that strings match specific date formats and fall within required temporal ranges.
• Empty Value Validations - Evaluates whether a value is empty based on its type, including zero-values and nil pointers.
• Mandatory Value Enforcement - Ensures required data is present by checking that a value is not empty.
• Null Value Validation - Verifies that interfaces, pointers, slices, and maps are not nil.
• Required Field Enforcement - Ensures a value is not blank, nil, or zero to satisfy mandatory field requirements.
• String Validation and Normalization - Enforces constraints on string inputs using custom rules and configurable error messages.
• Validation Error Customizations - Allows the user to override default failure text for built-in rules on a per-instance or global basis.
• Validation Error Formatters - Structures validation failures into keyed maps for serialization to JSON or human-readable strings.
• Validation Error Handlers - Defines custom failure text using dynamic placeholders to inject rule thresholds into error messages.
• Validation Libraries - Extensible validation for various data types.

Star history