Skip to content

kogosoftwarellc/open-api

master
Switch branches/tags
Code

Latest commit

The "const" keyword was added in OAS 3.1, largely as syntactic sugar for a single value enum. It's been a part of the JSON schema spec since draft-06 and seems to be more common out in the wild now.
9b58193

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
bin
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

@open-api Build Status Coveralls Status Gitter chat Greenkeeper badge

A Monorepo of various packages to power OpenAPI in node.

Quick Start Express

Quick Start Koa

Packages

Development

This monorepo uses lerna for development. See the root package.json for helpful scripts.

Typical Workflow for Contributors

Let's say you're working on a package under ./packages. Here's what you do:

  1. cd open-api
  2. npm run bootstrap
  3. npm t
  4. Make your changes.
  5. Do not bump the version in package.json. A maintainer will handle that once your PR is merged.
  6. Once you're satisfied with your changes:
  7. Create a new branch git checkout -b my-branch (in case you haven't done so already).
  8. ./bin/commit packages/<package_you're_working_on> 'commit message describing your change. can be multi line here. just close with a single quote like so:'
  9. Push your change to your fork
  10. Open a PR.

bin

Several scripts have been created to aid in the development of this monorepo (see ./bin). They assume that your $PWD is the root of the repository. Here is a brief summary of common actions:

  • Commit changes to a package - ./bin/commit packages/<package_to_commit> 'Commit message' (the commit message will be prepended with the package name e.g. <package_to_commit>: Commit message
  • These reduce boilerplate and are called from npm scripts in leaf repos.
    • nyc
    • tsc
    • mocha

LICENSE

The MIT License (MIT)

Copyright (c) 2018 Kogo Software LLC

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.