It is unit tested with 100% code coverage and can be considered fit for production.
The validation constraints can be declared in JSON and shared between clients and the server. One thing that is a bit unorthodox is that most validators will consider undefined values (,) valid values.I find it quite common that you want to have constraints on an optional attribute.One core value of this library is that nothing should be private or inaccessable.If you want to use async validation you need to use a runtime that supports Promises.
You can tell to use any A compatible promise implemention like this: There are already many validation libraries out there today but most of them are very tightly coupled to a language or framework.Or when making payments by "paperless" check over the phone or online.These routing numbers include a checksum digit which can be used to help verify if a given number is valid or not. You can usually find your own bank's routing number printed on your checks (look for a nine-digit number at the bottom center of the check).The number may not, in fact, be assigned to any financial institution.