npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

openapi-request-validator-generator

v1.0.6

Published

Generate code to validate request properties against an OpenAPI spec.

Downloads

11

Readme

openapi-request-validator-generator

Generate code to validate request properties against an OpenAPI spec.

Example

// Part 1. Here's how you generate the code (use this in a build script)

const generateOASValidationCode = require('openapi-request-validator-generator')

// Note that the ./generatedCode directory will be deleted if anything exists there currently
generateOASValidationCode('./path/to/oas.yaml', './generatedCode')


// Part 2. Here's how you use the generated code at runtime

// resource & method will be a specific resource and method from your OAS. The "oas" part comes from the filename of your OAS. If the spec file is named "yipee.yaml", and contains a resource GET /monkeys, then your generated filename would be "yipee_monkeys_get.js"

// each endpoint in your OAS will have a unique validator that you will need to import, as it's validation is specific to that endpoint

const validateRequest = require('./generatedCode/oas_resource_method.js') 

const request = {
  headers: {
    'content-type': 'application/json'
  },
  body: {},
  params: {},
  query: {foo: 'wow'}
};
const errors = validateRequest(request);
console.log(errors); // => undefined