Skip to content

Commit 8092100

Browse files
author
Ole Lensmar
authored
fixed formatting of Variable substitution table
1 parent ff37149 commit 8092100

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

versions/3.0.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1201,8 +1201,8 @@ The variables generated can be used in locations prescribed by the definition.
12011201
In all cases, _variables_ from request and responses may be substituted for link generation. The table below designates the source of the substitution value and the syntax for accessing it:
12021202

12031203
Source Location | reference identifier | example value | example reference | notes
1204-
---|:---|:---|:---
1205-
HTTP Method | `$method` | `/users/{$method}` | The allowable values for the `$method` will be those for the HTTP operation
1204+
---|:---|:---|:---|:---
1205+
HTTP Method | `$method` | `/users/{$method}` | The allowable values for the `$method` will be those for the HTTP operation
12061206
Requested content type | `$accepts` | `/users/3?format={$accepts}` |
12071207
Request parameter | `$request` | `/users/{$request.id}` | Request parameters must be declared in the `parameters` section for the operation or they cannot be used in substitution. This includes request headers
12081208
Request body | `$requestBody` | `/users/{$requestBody.user.uuid}` | For operations which accept payloads, references may be made to portions of the `requestBody` or the entire body itself

0 commit comments

Comments
 (0)