apiaryio / api-elements.js

Library for consuming API Elements in JavaScript

https://apielements.org/

apiaryio/api-elements.js Issues

Support readOnly on openapi2 (swagger)
Updated 3 years ago
OpenAPI 3 media type examples warning misses source map
Closed 3 years ago
Error when using the cli
Closed 3 years ago
OAS3 path name regex is overly restrictive
Closed 4 years ago1
Readme has a link to a dismissed library (fury-cli)
Closed 4 years ago1
Make errors emitted from core programatically inspectable
Updated 4 years ago
Documents using reserved API Element names as schema ids fail parsing
Updated 4 years ago
OAS 3 parser does not generate Accept header's for the response content-type
Closed 4 years ago
Schema's properties aren't supported
Closed 4 years ago2
Generated JSON Schemas do not contain $schema for draft-4
Closed 4 years ago
Message body serialization adapters
Updated 5 years ago
Template render error: Unable to call `item["value"]["toValue"]`, which is undefined or falsey
Closed 5 years ago3
API B Serializer throws template render error for given document
Closed 5 years ago4
Prevent duplicate IDs from being used in OAS 3 parser
Updated 5 years ago
OAS3 Security TODO
Updated 5 years ago
Array parameters in swagger is incorrectly converted into API Blueprint
Updated 5 years ago
Add support for default response status code
Updated 5 years ago
Extract minim's legacy 0.6 serialiser to api-elements.js
Updated 5 years ago
OAS 3 parser can crash during handling of value generation
Closed 5 years ago
Provide connivence accessors on SourceMap's for begin/end line/column
Updated 5 years ago
Add support for parameters in media types for OAS 3
Closed 5 years ago
Rethink Fury API
Updated 5 years ago1
JSON Body generation of array of object doesn't respect object example
Closed 5 years ago
Incorporate deckardcain
Updated 5 years ago4
Support 'schema' in Parameter Object in OpenAPI 3
Updated 5 years ago
Swagger: unhandled `throw` from function `lookupReference`
Closed 5 years ago3
OAS3: Security schemes in components should be an object
Updated 5 years ago
OAS3: parseMap vs parseComponentObjectMember need to be streamlined
Updated 5 years ago
Generate JSON example body from schema object
Closed 5 years ago4
Generating JSON body for unknown schema formats
Closed 5 years ago1
Provide a "remote" Fury adapter
Closed 5 years ago1
Fury catches exceptions happening in the callback
Closed 5 years ago
Support for data structure generation when referencing property from another schema
Closed 5 years ago
Add Snyk monitoring
Closed 5 years ago1
Fury returns both error and the parse result
Closed 5 years ago3
How to easily access source map's line and column?
Closed 5 years ago4
The OAS3 parser crashes on status code in form of a number
Closed 5 years ago5
Get ready for npm's RFC 10
Closed 5 years ago
Update fury toolchain in Apiary
Closed 5 years ago1
Integrate OpenAPI 3 into Apiary
Closed 5 years ago2
Generate JSON Schema messageBody asset from OpenAPI 3 Schema
Updated 5 years ago1
Support requestBody in Operation Object
Closed 5 years ago
OAS 3 detection should not require quotes around openapi version number
Closed 5 years ago
Implement schema parser
Updated 5 years ago
Docs are not being built
Closed 5 years ago
Parse request body 'description'
Closed 5 years ago
Integrate Media Type Object Parser into Request Parser
Closed 5 years ago
Ensure uniqueness of emitted API Element ids
Updated 5 years ago1
Support 'description' in response object parser
Closed 5 years ago
Add support for response status code ranges
Updated 5 years ago