Wrap zod validation errors in user-friendly readable messages
No description provided.
Decorator-based property validation for classes.
No description provided.
React Hook Form validation resolvers: Yup, Joi, Superstruct, Zod, Vest, Class Validator, io-ts, Nope, computed-types, TypeBox, arktype, Typanion, Effect-TS and VineJS
Node validation utility functions for Docusaurus packages.
Promise wrapped interactor pattern for NodeJS
TLDS list for domain validation
Runtime validation and processing of JavaScript types
No description provided.
Client-side form validation made easy
Provides the ability to initiate haptic feedback on the controllers connected to an interactor for the Unity software.
An implementation of the Unicode UTS #46: Unicode IDNA Compatibility Processing
mjml-validator
Internationalized number formatting and parsing utilities
Library for reporting click, conversion and view metrics using the Algolia Insights API
Statoscope extension that collects stats validation result
Performant, flexible and extensible forms library for React Hooks
URI validation functions
[](https://npmjs.org/package/@standard-community/standard-json "View this project on NPM") [
Sheet-specific data validation commands, services, and Facade APIs for Univer Sheets.
Data validation UI for Univer Sheets.
Reusable JSON Schema (Draft 04) validation library for Expo
Lightweight, zero-dependency validation for Interactor service objects. Supports presence, format, length, inclusion, numericality, and nested validations.
An implementation of the Command Pattern for Ruby with ActiveModel::Validations inspired by the interactor gem. Rich support for attributes, callbacks, and validations, and thread safe performance methods.
Adds parameter validation and error control to interactor
Just a simple, ready to use interactor implementation with built in validation of input params
Interactor + Form Object + ActiveModel::Validation
Interactors are a pattern for structuring your business logic into units. They have a flexible context that they pass between them, which makes them easy-to-write, but hard-to-understand after you've written them. Much of this confusion comes from not knowing what the interactor is supposed to take as input and what it's expected to produce. Enter contracts. Contracts allow you define, up front, a contract both for the input of an interactor, known as expectations, and the output of it, known as promises. Additionally, you can define a handler for what happens when an interactor violates its contracts, known as a breach. Declaring these contracts can help define your interface and make it easier to understand how to use an interactor. They form both documentation and validation for your business logic.
A small dry-rb-based base service/interactor with optional contract validation.