api-elements
api-elements copied to clipboard
API Elements is a structure for describing APIs and the complex data structures used within them.
I'm opening this issue to create a discussion around how we should handle the evolution of API Elements. I would like to involve relevant parties when introducing new element types,...
Re https://github.com/apiaryio/drafter/pull/653#discussion_r232318730, the specification doesn't state if line and column numbers are 0-indexed or 1-indexed. /c @klokane @tjanc
The headings do not have unique links (clicking on Template permalink gets me to the first Template heading in the document).
Currently, HTTP Headers is a subtype of Object Element. But a HTTP Header can occur multiple times, which means HTTP Headers should be an array of HTTP Header. ### Proposal...
Moved from https://github.com/refractproject/refract-spec/issues/42
There are discrepancies in the API Blueprint parser and Swagger adapter because of source map positions are treated differently (https://github.com/apiaryio/fury.js/issues/63). In Swagger adapter, the source map represents the position of...
Annotation Code's are difficult to use for any meaning as they are not universally unique. One parser can treat one code with some meaning and another parser could treat the...
When should we use copy element and when should we use description meta?
Resolves #18 Please see the issue above for explanation on this PR. Also, note I bumped the version of the specification to 1.1.0. cc: @paraskakis @netmilk @kylef
I've been thinking about this for a long time and I think it would be great if a warning or error annotations could provide hints to users on what to...