Promised based validation library
Inquirer input text prompt
Inquirer password prompt
Simple and robust resource pool for node.js
Validation to be used with @alifd/field
Inquirer multiline editor prompt
Inquirer number prompt
File scanning module for Node.js
Give me a string and I'll tell you if it's a valid npm package name
Resolve any installed ES6 compatible promise
Parser/validator for OpenAPI 3.x definitions
No description provided.
Wrapper for `xmllint`. Easy validation of XML. XML Schemas and DTDs supported. Zero dependencies.
Node.js library for SAML SSO
Bare bones Promises/A+ implementation
Creates a Promise that waits for a single event
Retries a function that returns a promise, leveraging the power of the retry module.
A Promise-compatible abstraction that defers resolving/rejecting promises to another closure.
Statoscope stats validator
Email address and domain validation
TypeScript definitions for validate-npm-package-name
Test whether an object looks like a promises-a+ promise
A lightweight library that provides tools for organizing asynchronous code
Validates whether a string matches the production for an XML name or qualified name
LightService plugin adding DSL for expected/promised keys validation
It sure would be awesome if ActiveResource actually allowed us to do client-side validation of our ActiveResource objects like their documentation promises: http://apidock.com/rails/ActiveResource/Base
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.