This is more of a development problem and does not affect users as it is with dev dependencies. When cloning the repository and running yarn, yarn warns about incorrect peer dependencies:

$ git clone https://github.com/apiaryio/dredd.git dredd-clean
Cloning into 'dredd-clean'...
remote: Enumerating objects: 54, done.
remote: Counting objects: 100% (54/54), done.
remote: Compressin

I have a file, falcon.apib that I want to run with the http or mock commands. Execution is done via

docker run -v $(PWD)/docs:/docs --rm quay.io/bukalapak/snowboard http /docs/falcon.apib

(latest docker image, I triple-checked that)

But no port is exposed from the container:

docker ps
CONTAINER ID        IMAGE                         COMMAND                  CREATE

Creating a new issue just to keep tabs.
#120

Related to the above pull request.

Need an option in drakov.run to watch the md files and reload.

Similar to:

grunt.registerTask('mock-api', 'Start drakov server', function() {
var done = this.async();

var drakovOptions = {
  sourceFiles: './doc/*.md',
  serverPort: 3000,
  autoOptions: true,
  delay: 1000,
  watch: true
};

drakov.run(drakovOp

"## [/resourcename]" shows "valid document" but the resulting code doesn't work properly in the documentation, ie no machine column or console

Input URL: http://docs.shipstation.apiary.io/api-description-document

Contains headers with multiple HTTP verbs?

## Get/Delete Order [/orders/{orderId}]

Generated swagger (excerpts):

          "parameters": [
            {
              "name": "storeId",
              "in": "path",
              "description": "A unique ID generated by ShipStation and assign

Looks like a bug in Dredd. Here it should be consistently reproducible. I found it out some time ago, but filing this thanks to @dariagrudzien playing around with the contents of this repo.

CircleCI

Travis CI

<img width="548" alt="image" src="http

Data Structure

• Access Token Request
• Refreshing Tokens
• Revoking Access Tokens

Responses

POST

• Access Token Request
• Refreshing Tokens
• Revoking Access Tokens

Documented & Explained

• Authorization Code Grant Flow
• Implicit Grant Flow
• Scopes
• Redirect URIs
• Making Authenticated Requests

Currently, all the api doc macros are meant to be used within the controllers. It might be better if some definitions (i.e. shared parameters, warnings etc.) would be defined in a central place. Also, sometimes it might be a better idea to define the route descriptions in a central place as well. We should define best practices for this and figure out how to handle centrally defined api macros.

https://swagger.io/docs/specification/describing-parameters/#common-parameters

Currently common parameters are duplicated across path methods, resulting in a lot of duplicate lines of code in generated specifications. Migrate these up into common parameters and save a bunch of space.

The apiblueprint documentation for the URI parameters section shows the usage of a default value
https://apiblueprint.org/documentation/specification.html#def-uriparameters-section

However there seems to be some issues with it:

• if I define it alone under a parameter, it doesn't get displayed in the result
• if I define it alongside a "Members" field, parsing fails