Swagger 2.0 parser adapter for Fury.js
JavaScript
Latest commit e655991 Jan 3, 2017 @pksunkara pksunkara committed on GitHub Merge pull request #97 from apiaryio/XVincentX/update-json-schema-faker
Update json-schema-faker

README.md

Fury Swagger 2.0 Adapter

Build Status Coverage Status NPM version License

This adapter provides support for parsing Swagger 2.0 in Fury.js. It does not yet provide a serializer.

Try the Fury adapter in your browser to convert Swagger 2.0 documents into Refract elements.

Install

npm install fury-adapter-swagger

Usage

import fury from 'fury';
import swaggerAdapter from 'fury-adapter-swagger';

fury.use(swaggerAdapter);

fury.parse({source: '... your Swagger 2.0 document ...'}, (err, result) => {
  if (err) {
    console.log(err);
    return;
  }

  // The returned `result` is a Minim parse result element.
  console.log(result.api.title);
});

Parser Codes

The following codes are used by the parser when creating warning and error annotations.

Warnings:

Code Description
2 Source maps are unavailable due either to the input format or an issue parsing the input.
3 Data is being lost in the conversion.

Errors:

Code Description
1 Error parsing input (e.g. malformed YAML).
4 Swagger validation error.
5 Swagger to Refract converter error (JS exception).

Swagger Vendor Extensions

Some Swagger Vendor extensions found in source Swagger documents are converted into the output API Element as extension elements.

The following locations of vendor extensions are supported:

  • within the info object
  • within the paths object
  • within the path-item object
  • within the operation object
  • within the responses object

These vendor extensions will be available as extensions using the relation https://help.apiary.io/profiles/api-elements/vendor-extensions/.