ramllint

RAML is a language for modeling RESTful APIs. By design, it does not enforce any style rules on how to consistently document APIs, because not all projects will require the same level of rule enforcement. However, it can often be useful to enforce uniform rules and standards across a group of related APIs to ensure consistency and uniformity across multiple teams or business units.

RAML Linter is a static analysis, linter-like, utility that will enforce rules on a given RAML document, ensuring consistency and quality.

Installing

npm install -g ramllint

Using the Linter

RAML Linter can be used either as a library or as a command line utility.

Library

Using the library in code provides the most flexibility, offering error handling and the ability to parse the full results for: error, warning, and info log entries.

var Linter = require('ramllint'),

    ramllint = new Linter();

ramllint('./path/to/api.raml', function (results) {
   // NOTE: results will only contain 'error' and will exclude 'warning' and 'info'
   // to get an array of all log entries use: `ramllint.results()`

  if (!results.length) {
    // no errors, all rules are satisfied
  } else {
    // errors
  }
});

Command Line

If you are in the same directory as your RAML document:

ramllint

If your RAML document is in another directory:

ramllint path/to/api.raml

(npm) Scripts

Below is a list of commands available via npm run for you convenience:

• npm run cover for TravisCI only
• npm run doc
  1. Remove the docs/ directory to start clean
  2. Generate documentation pages (JSDoc) in docs/
  3. Create code coverage report (Istanbul) docs/coverage/lcov-report/
  4. Create code statistics report (Plato) docs/coverage/
• npm run doc:pub for publishing docs/ to gh-pages
• npm run lint - static code analysis and code style linting
  1. JShint
  2. ESlint
• npm run quality - runs lint and code coverage
• npm test - runs unit tests (Mocha)
• npm run watch - watches test/ and src/ for changes and re-runs tests

Documentation

1. Code Documentation
2. Code Coverage Report
3. Static Code Analysis

Contributing

1. Fork this repository
2. git clone
3. npm install
4. Create a working branch
5. Write code and tests
6. Submit Pull Request

This project aims to maintain a high level of unit test code coverage. All pull requests must be accompanied by appropriate test cases, and all tests must pass in order to be considered for merge.

For detailed rules on contributions, please refer to our contribution guidelines.