The most powerful data validation library for JS
-
Updated
Sep 3, 2021 - JavaScript
{{ message }}
The most powerful data validation library for JS
Execute one command (or mount one Node.js middleware) and get an instant high-performance GraphQL API for your PostgreSQL database!
A tool for generating code based on a GraphQL schema and GraphQL operations (query/mutation/subscription), with flexible support for custom plugins.
Create GraphQL schema and resolvers with TypeScript, using classes and decorators!
A lightweight library for converting complex objects to and from simple Python datatypes.
A simple and composable way to validate data in JavaScript (and TypeScript).
Python Data Structures for Humans™.
SchemaSpy code home
A database migration tool. Supports SQL migrations and Go functions.
Featureful configuration management library for Node.js
AutoForm is a Meteor package that adds UI components and helpers to easily create basic forms with automatic insert and update events, and automatic reactive validation.
Squasher - squash your old migrations in a single command
A library of custom GraphQL Scalars for creating precise type-safe GraphQL schemas.
Free database schema discovery and comprehension tool
Looks like it should be "Not all child routes satisfy compojure.api.routes/Routing."
Maybe a fix could use (str ::Routing) or some derivative
-Victor
Describe the bug
Unnecessary text explaining the project migration history maximum display count when there is no migration history at all.
Steps or screenshots to reproduce the behavior
Toolkit for generating complex GraphQL Schemas on Node.js
Here is an example of current error message:
The 'email_address' field must not be empty.
Is there a way to pass field label into schema so the error message is displayed like so:
The 'Email Address' field must not be empty.
I know we can use custom messages for each field but curious if there's a lazier approach here :)
Add some validation checks for mongo operators that can't be done by SimpleSchema. See longshotlabs/meteor-simple-schema#9.
Similar to the Email validator.
When users run a mutator (e.g. set-annotations), the output doesn't tell them which files changed. The only way a user can figure out which files were affected is by looking through them manually or doing git status or however they might normally be notified of changes to files.
It would be nice if we were able to notify the user which files changed as a result
Add a description, image, and links to the schema topic page so that developers can more easily learn about it.
To associate your repository with the schema topic, visit your repo's landing page and select "manage topics."
The title might seem a bit vague but I don't know how to describe it any better tbh :-)
Anyway this is what happened: I got some 500 responses from the schema registry and all I could see in the logs was :
The logs di