Skip to content

Commit

Permalink
docs(TryItOut): increse documentation coverage
Browse files Browse the repository at this point in the history
  • Loading branch information
char0n committed Apr 24, 2020
1 parent 45031b2 commit 298ef34
Showing 1 changed file with 189 additions and 0 deletions.
189 changes: 189 additions & 0 deletions docs/TRY_IT_OUT_EXECUTOR.md
@@ -0,0 +1,189 @@
#### TryItOut Executor

TryItOut Executor is an OpenAPI specific HTTP client for OAS operations.
It maps an OAS operation and values into an HTTP request.

To execute an OAS operation, you need to provide TryItOut Executor with various properties.

Type notations are formatted like so:

- `String=""` means a String type with a default value of `""`.
- `String=["a"*, "b", "c", "d"]` means a String type that can be `a, b, c, or d`, with the `*` indicating that `a` is the default value.

Property | Description
--- | ---
`spec` | `Object`, **REQUIRED**. OpenAPI definition represented as [POJO](https://en.wikipedia.org/wiki/Plain_old_Java_object).
`operationId` | `String`. Unique string used to identify an operation. If not provided, `pathName` + `method` must be used instead.
`pathName` | `String`. OpenAPI defines a unique operation as a combination of a path and an HTTP method. If `operationId` is not provided, this property must be set.
`method` | `String=["GET", "HEAD", "POST", "PUT", "DELETE", "CONNECT", "OPTIONS", "TRACE", "PATCH"]`. OpenAPI defines a unique operation as a combination of a path and an HTTP method. If `operationId` is not provided, this property must be set.
`parameters` | `Object`. Parameters object, eg: `{ q: 'search string' }`. Parameters not defined in `spec` will be ignored.
`securities` | `Object`. Maps security schemes to a request. Securities not defined in `spec` will be ignored. <br/><br/>*Examples*<br /><br /> *Bearer:* `{ authorized: { BearerAuth: {value: "3492342948239482398"} } }` <br /><br /> *Basic:* `{ authorized: { BasicAuth: { username: 'login', password: 'secret' } } }` <br /><br /> *ApiKey:* `{ authorized: { ApiKey: { value: '234934239' } } }` <br /><br /> *oAuth2:* `{ authorized: { oAuth2: { token: { access_token: '234934239' } } } }`
`requestContentType` | `String`. Sets [appropriate media type](https://swagger.io/docs/specification/describing-request-body/) for request body, e.g. `application/json`. If supplied media type is not defined for the request body, this property is ignored.
`responseContentType` | `String`. Expect [appropriate media type](https://swagger.io/docs/specification/describing-responses/) response, e.g. `application/json`. Creates an `Accept` header in `Request` object.
`http` | `Function=Http`. A function with an interface compatible with [HTTP Client](HTTP_CLIENT.md).
`userFetch` | `Function=cross-fetch`. Custom **asynchronous** fetch function that accepts two arguments: the `url` and the `Request` object and must return a [Response](https://developer.mozilla.org/en-US/docs/Web/API/Response) object. More info in [HTTP Client](HTTP_CLIENT.md) documentation.

For all later references, we will always use following OpenAPI 3.0.0 definition when referring
to a `spec`.

```yaml
openapi: 3.0.0
info:
title: Testing API
version: 1.0.0
components:
schemas:
user:
properties:
id:
type: integer
securitySchemes:
BasicAuth:
type: http
scheme: basic
ApiKey:
type: apiKey
in: header
name: X-API-KEY
BearerAuth:
type: http
scheme: bearer
oAuth2:
type: oauth2
flows:
implicit:
authorizationUrl: 'https://api.example.com/oauth2/authorize'
scopes:
read: authorize to read
servers:
- url: 'http://localhost:8080'
paths:
/users:
get:
operationId: getUserList
description: Get list of users
security:
- BasicAuth: []
BearerAuth: []
ApiKey: []
oAuth2: []
parameters:
- name: q
in: query
description: search query parameter
schema:
type: string
responses:
'200':
description: List of users
content:
application/json:
schema:
$ref: '#/components/schemas/user'
```

Use [swagger editor](https://editor.swagger.io/) to convert this [YAML](https://en.wikipedia.org/wiki/YAML) OpenAPI definition
to [JSON](https://en.wikipedia.org/wiki/JSON); `File` -> `Convert and save as JSON`. We'll assign this `JSON` to variable called
`pojoDefinition` and use it in later examples.

Above OpenAPI definitions describes following API implemented in `node.js`:

```js
const http = require('http');

const getUserList = (req, res) => {
res.setHeader('Content-Type', 'application/json');
res.writeHead(200);
res.end('[{"id":"value"}]');
};

const requestListener = (req, res) => {
if (req.url.startsWith('/users')) {
getUserList(req, res);
} else {
res.setHeader('Content-Type', 'text/plain');
res.writeHead(404);
res.end('Not found');
}
};

const server = http.createServer(requestListener);
server.listen(8080);
```

##### Executing an operation

Executing an OAS operation is as simple as calling `SwaggerClient.execute` static method.

*Using operationId*

```js
import SwaggerClient from 'swagger-client';

SwaggerClient.execute({
spec: pojoDefinition,
operationId: 'getUserList',
parameters: { q: 'search string' },
securities: { authorized: { BearerAuth: "3492342948239482398" } },
}); // => Promise.<Response>
```

*Using unique pathName + method combination*

```js
import SwaggerClient from 'swagger-client';

SwaggerClient.execute({
spec: pojoDefinition,
pathName: '/users',
method: 'get',
parameters: { q: 'search string' },
securities: { authorized: { BearerAuth: "3492342948239482398" } },
}); // => Promise.<Response>
```

###### Alternate API

It's also possible to call `execute` method from `SwaggerClient` instance.


```js
import SwaggerClient from 'swagger-client';

new SwaggerClient({ spec: pojoDefinition, authorizations: { BearerAuth: "3492342948239482398" } })
.then(
client => client.execute({
operationId: 'getUserList',
parameters: { q: 'search string' },
})
); // => Promise.<Response>
```

##### Building a Request

You can build a `Request` object from an OAS operation and feed it later to the [HTTP Client](HTTP_CLIENT.md).

```js
import SwaggerClient from 'swagger-client';

const request = SwaggerClient.buildRequest({
spec: pojoDefinition,
operationId: 'getUserList',
parameters: { q: 'search string' },
securities: { authorized: { BearerAuth: "3492342948239482398" }},
responseContentType: 'application/json',
});
/*
* {
* url: 'http://localhost:8080/users?q=search%20string',
* credentials: 'same-origin',
* headers: {
* accept: 'application/json',
* Authorization: 'Bearer 3492342948239482398'
* },
* method: 'GET'
* }
*/

SwaggerClient.http(request); // => Promise.<Response>
```

0 comments on commit 298ef34

Please sign in to comment.