Not to use! Work in progress!!!Node.js module to compare nickname, email, password with a pattern.
The ajv-8 based validator for @rjsf/core
React Hook Form validation resolvers: Yup, Joi, Superstruct, Zod, Vest, Class Validator, io-ts, Nope, computed-types, TypeBox, arktype, Typanion, Effect-TS and VineJS
Info about node `exports` field support: version ranges, categories, etc.
Performant, flexible and extensible forms library for React Hooks
React Form Component
Validate identifier/keywords name
A package of Essential JS 2 input components such as Textbox, Color-picker, Masked-textbox, Numeric-textbox, Slider, Upload, and Form-validator that is used to get input from the users.
A library for validating credit card fields
validate form asynchronous
Another JSON Schema Validator
Validate plugin/preset options
Validate form asynchronous
React Form Component
Additional JSON-Schema keywords for Ajv JSON validator
React High Order Form Component
Simple validator for forms designed with material-ui v1/v3/v4/v5 components.
mashup of lodash with checkit module
Decorator-based property validation for classes.
Git commit-msg hook validator
Another JSON Schema Validator
String validation and sanitization
Form processor for filter and validation form data
Migrate JSON-Schema to draft-06
Custom form builder to create forms and inputs that work with Bootstrap 3. Also automatically sets pattern and required HTML5 attributes based on validators on domain objects.
Regex is a versatile Ruby library designed to simplify form validation by providing a collection of regular expressions tailored for common form fields. Whether you're building a web application, validating user input, or processing form submissions, this library offers a set of regex patterns that can be easily integrated into your validation logic.
a Rails gem that allows you to validate a URL entered in a form. It validates if the URL exists by hitting it with a HEAD request. The improved version includes retries for common patterns when the head request is refused before giving a failure notice. It also looks up a SITE_URL constant to the user agent in the headers. Also has the option to also check that the URL returns content of a specified type.
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.