Z

Results 21 issues of Z

Add option to measure and report time spent in `ParseBlueprint()`. Future: consider setting a parsing timeout and abort parsing when timeout is reached.

enhancement

Direct support for API authentication. ## RFC proposals - [API Blueprint RFC 0002: Authentication Framework](https://github.com/apiaryio/api-blueprint-rfcs/blob/master/draft/0002-authentication.md) - [API Blueprint RFC 0003: Basic Authentication Scheme](https://github.com/apiaryio/api-blueprint-rfcs/blob/master/draft/0003-authentication-basic.md) - [PR: OAuth 2 Authentication Scheme](https://github.com/apiaryio/api-blueprint-rfcs/pull/6)

type (2): Feature
status (2): RFC
scope (1): Language
priority (2): Next

Support for multiple API blueprint files within one API.

type (2): Feature
status (1): Idea
scope (1): Language

Add the possibility to use [Markdown links](http://daringfireball.net/projects/markdown/syntax#link) wherever an asset is expected (e.g. a payload body or schema).

type (2): Feature
status (1): Idea
scope (1): Language

Explain "inline" actions `# PUT /post/{id}` or `# Update [PUT /post/{id}]` in the advanced tutorial. As used in the API Blueprint specification https://github.com/apiaryio/api-blueprint/blob/master/API%20Blueprint%20Specification.md#example-9. Originally suggested at https://apiblueprint.slack.com/archives/blueprint/p1459888810000137

scope (2): Documentation
status (1): Idea

Using the information from the [Attributes section](https://github.com/apiaryio/api-blueprint/blob/master/API%20Blueprint%20Specification.md#def-attributes-section) and the [Action section](https://github.com/apiaryio/api-blueprint/blob/master/API%20Blueprint%20Specification.md#def-action-section) The API Blueprint parser should be able to render Hypermedia media types on behalf of the user. For example...

type (2): Feature
status (1): Idea
scope (1): Language

Use MSON syntax for description of URI parameters and HTTP headers RFC draft PR: https://github.com/apiaryio/api-blueprint-rfcs/pull/3

type (2): Feature
status (2): RFC
scope (1): Language

Given this blueprint (currently valid syntax): ``` apib # Author [/author/{id}] - Parameters - id (number) - Id of the author - Attributes - email (string) - Email of the...

type (2): Feature
status (2): RFC
scope (1): Language

Separate protocol layer from the description of the API semantics. The idea is to move protocol specifics from existing Resource and Action sections into new sections. This breaks the API...

type (2): Feature
status (1): Idea
scope (1): Language

Following the [Resource Blueprint Concept](https://github.com/resource-blueprint/resource-blueprint) the API Blueprint should offer description of the API state machine. This will benefit both the conceptual design of an API and the testing of...

type (2): Feature
status (1): Idea
scope (1): Language