re: πŸŽ‰ Deno: 1.0 officially scheduled on May, 13! Review of the features VIEW POST


Guys, this is an awesome node replacement but still lacking openapi3 validation (ajv) like in node. I’d like to take part in transporting the existing ajv code to deno (which might be possible) but I cannot assess the quantity of work. Maybe you think it would be better off to implement an own deno openapi3 validator?

code of conduct - report abuse