jeengbe / vality Goto Github PK

Add a date guard into vality. options could specify a minDate and maxDate, to be valid.

Add a type that is included in Parse and therefore possibly part of the api's output, but not included in ParseIn, so we can have types that are visible in TS but are not validated succesfully. In case we have some types that are being set on the api. E.g. createdAt, createdBy, permissions..

Fix deprication Warning of main

(node:17712) [DEP0128] DeprecationWarning: Invalid 'main' field in '.../vality/package.json' of './dist/index.js'. Please either fix that or report it to the module author

The relational type's TS signature is not compatible with its validator.
Currently is string (though configurable), but validation is always int number>0.

this should also be globally configureable. Also relation is a type that could specifically be null, if optional.

(Sorry to intrude here—this repository is above my pay grade—but I often poke around GitHub to stretch my knowledge. I enjoyed a question/comment by @jeengbe made elsewhere regarding "deployments," accompanied by a fabulous graph, so I wanted to see his work, leading me here.)

The Issue: Using Vivaldi (chromium flavor), on the first attempt at browsing to any ts-vality.io domain page, the result is an error message: "This site can’t be reached. Check if there is a typo in ts-vality.io."

I attempted Firefox, Safari, and Chrome, also incognito. I don't use a proxy/firewall. I emptied the cache and temporarily turned on all permissions on at least one browser. I could not, under any of these circumstances, reach your website. I'm in the U.S. on MacOS. The Vality repo seems currently active, so I'm dropping a line.