swagger schema extensions (^x-) in info section are not allowed

[subeeshcbabu-zz]

Sample API - https://api.apis.guru/v2/specs/glugbot.com/1/swagger.json

The app fails with following schema validation error for schema extensions in info section

ValidationError: child "info" fails because ["x-origin" is not allowed, "x-preferred" is not allowed, "x-providerName" is not allowed]

Extensions:

   "x-origin": {
      "format": "swagger",
      "url": "http://www.glugbot.com/api-docs",
      "version": "1.2"
    },
    "x-preferred": true,
    "x-providerName": "glugbot.com"

[kenjones-cisco]

Have you considered using https://www.npmjs.com/package/swagger-parser as the parser / validator instead of maintaining the enjoi custom built one?

I know it definitely works with vendor extensions in the info section.

Features:

• Parses Swagger specs in JSON or YAML format
• Validates against the Swagger 2.0 schema and the Swagger 2.0 spec
• Resolves all $ref pointers, including external files and URLs
• Can bundle all your Swagger files into a single file that only has internal $ref pointers
• Can dereference all $ref pointers, giving you a normal JavaScript object that's easy to work with
• Configurable caching of external files and URLs
• Tested in Node, IO.js, and all modern web browsers on Mac, Windows, Linux, iOS, and Android
• Tested on over 200 real-world APIs from Google, Instagram, Cisco, etc.
• Supports circular references, nested references, back-references, and cross-references
• Maintains object reference equality — $ref pointers to the same value always resolve to the same object instance

[subeeshcbabu-zz]

Yes. Huge plus for swagger parser and json validator. I am working on the next major version of the router, that is going to replace enjoi with swagger-parser and is-my-json-valid json validator. https://github.com/krakenjs/swaggerize-routes/milestone/1 Expect a PR by end of this week.

[nakamorichi]

How is the next version coming? I need to get the vendor extensions working...

[subeeshcbabu-zz]

sorry this PR got delayed. Working on it now. will update the status soon.