You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: hull-vidispine-addon/README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -186,6 +186,7 @@ Describes a particular entity on a subresource on an endpoint which is communica
186
186
| `contentType` | The content type header for POST or PUT of the entity `config` and the accept header for all calls. Supported choices are `application/json`, `application/xml` and `text/plain`. Defaults to `application/json`. | `application/json` | `POST` <br> `PUT`
187
187
| `postQueryParams` | Query Parameters to add to the Url of a POST command. Not a frequent use case but required to submit for example the `guid` of a UseCaseDefinition to migrate. | | `POST`
188
188
| `putInsteadOfPost` | Some APIs use PUTting instead of POSTing for creation of new entities. If the subresource uses PUTting instead of POSTing, set this parameter to `true`. | `false` | `POST` <br> `PUT`
189
+
| `multiPartFormData` | Setting this switch to `true` allows to POST single files as multiPartFormData. If `true`, the `config` section is expected to contain a single deliberately named key whose value is the relative file path to the file which is to be POSTed. For example, the following data will post the `myicon.svg` file to the API endpoint: <br><br>`multiPartFormData:` `true`<br>`config:`<br>  `files:` `icons/myicon.svg`<br><br>Physical files need to be stored under `files/hull-vidispine-addon/installation/sources` or a direct subfolder of this path.| `false` | `POST`
189
190
| `putUriExcludeIdentifier` | Some APIs handle PUTting of entities by PUTing to the parent resource and specifying the entity to create in the body. If the subresource handles PUTting in that way, set this parameter to `true`. If `false` or unspecified, PUT calls will be made to the path which ends with the entities __identifier__. | `false` | `PUT`
190
191
| `putQueryParams` | Query Parameters to add to the Url of a PUT command. | | `PUT`
191
192
| `remove` | The entity will be DELETEd if it exists. If both `register` and `remove` is true, any found entity is first removed if it exists before it is being created. | `false` | `DELETE`
0 commit comments