redoc/docs/redoc-vendor-extensions.md

109 lines
3.3 KiB
Markdown
Raw Normal View History

2016-02-01 20:23:13 +03:00
# ReDoc vendor extensions
ReDoc makes use of the following [vendor extensions](http://swagger.io/specification/#vendorExtensions)
2016-02-01 20:49:57 +03:00
### <a name="infoObject"></a>[Info Object](http://swagger.io/specification/#infoObject) vendor extensions
2016-02-01 20:23:13 +03:00
#### <a name="x-logo"></a> x-logo
2016-02-01 20:38:21 +03:00
| Field Name | Type | Description |
| :------------- | :-----------: | :---------- |
| x-logo | [Logo Object](#logoObject) | The information about API logo |
2016-02-01 20:23:13 +03:00
2016-02-01 20:49:57 +03:00
###### Usage in Redoc
2016-02-01 20:23:13 +03:00
`x-logo` is used to specify API logo. The corresponding image are displayed just above side-menu.
2016-02-01 20:49:57 +03:00
#### <a name="logoObject"></a>Logo Object
2016-02-01 20:23:13 +03:00
The information about API logo
2016-02-01 20:49:57 +03:00
###### Fixed fields
2016-02-01 20:38:21 +03:00
| Field Name | Type | Description |
| :-------------- | :------: | :---------- |
| url | string | The URL pointing to the spec logo. MUST be in the format of a URL
| backgroundColor | string | background color to be used. MUST be in [CSS color syntax](https://developer.mozilla.org/en/docs/Web/CSS/color) |
2016-02-01 20:23:13 +03:00
2016-02-01 20:49:57 +03:00
###### x-logo example
json
```json
2016-02-01 20:23:13 +03:00
{
"info": {
"version": "1.0.0",
"title": "Swagger Petstore",
"x-logo": {
"url": "https://rebilly.github.io/ReDoc/petstore-logo.png",
"backgroundColor": "white"
}
}
}
```
2016-02-01 20:49:57 +03:00
yaml
2016-02-01 20:23:13 +03:00
```yaml
2016-02-01 20:49:57 +03:00
info:
version: "1.0.0"
title: "Swagger Petstore"
x-logo:
url: "https://rebilly.github.io/ReDoc/petstore-logo.png"
backgroundColor: "white"
2016-02-01 20:23:13 +03:00
```
### [Tag object](http://swagger.io/specification/#tagObject) vendor extensions
#### <a name="x-traitTag"></a> x-traitTag
2016-02-01 20:38:21 +03:00
| Field Name | Type | Description |
| :------------- | :------: | :---------- |
| x-traitTag | boolean | In Swagger two operations can have multiply tags. This property distinguish between tags that are used to group operations (default) from tags that are used to mark operation with certain trait (`true` value) |
2016-02-01 20:23:13 +03:00
2016-02-01 20:49:57 +03:00
###### Usage in Redoc
2016-02-01 20:23:13 +03:00
Tags that have `x-traitTag` set to `true` are listed in side-menu but don't have any subitems (operations). Tag `description` is rendered as well.
This is useful for handling out common things like Pagination, Rate-Limits, etc.
2016-02-01 20:49:57 +03:00
###### x-traitTag example
json
2016-02-01 20:23:13 +03:00
```json
{
"name": "Pagination",
"description": "Pagination description (can use markdown syntax)",
"x-traitTag": true
}
```
2016-02-01 20:49:57 +03:00
yaml
2016-02-01 20:23:13 +03:00
```yaml
name: Pagination
description: Pagination description (can use markdown syntax)
x-traitTag: true
```
### [Operation Object](http://swagger.io/specification/#operationObject) vendor extensions
#### <a name="x-code-samples"></a> x-code-samples
2016-02-01 20:38:21 +03:00
| Field Name | Type | Description |
| :------------- | :------: | :---------- |
2016-02-01 20:49:57 +03:00
| x-code-samples | [ [Code Sample Object](#codeSampleObject) ] | A list of code samples associated with operation |
2016-02-01 20:23:13 +03:00
2016-02-01 20:49:57 +03:00
###### Usage in ReDoc
`x-code-samples` are rendered on the right panel of ReDoc
2016-02-01 20:23:13 +03:00
2016-02-01 20:49:57 +03:00
#### <a name="codeSampleObject"></a>Code Sample Object
2016-02-01 20:23:13 +03:00
Operation code sample
2016-02-01 20:49:57 +03:00
###### Fixed fields
2016-02-01 20:38:21 +03:00
| Field Name | Type | Description |
| :---------- | :------: | :----------- |
| lang | string | Code sample language. Value should be one of the following [list](https://github.com/github/linguist/blob/master/lib/linguist/popular.yml) |
| source | string | Code sample source code |
2016-02-01 20:23:13 +03:00
2016-02-01 20:49:57 +03:00
###### Code Sample Object example
json
```json
2016-02-01 20:23:13 +03:00
{
"lang": "JavaScript",
"source": "console.log('Hello World');"
}
```
2016-02-01 20:49:57 +03:00
yaml
2016-02-01 20:23:13 +03:00
```yaml
2016-02-01 20:49:57 +03:00
lang: JavaScript
source: console.log('Hello World');
2016-02-01 20:23:13 +03:00
```