diff options
| author |  Vyr Cossont <VyrCossont@users.noreply.github.com> | 2024-06-14 01:11:41 -0700 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2024-06-14 10:11:41 +0200 |
| commit | b789fe2bc72a1b1bca50da498ae22c10a4e7acc2 (patch) | |
| tree | d43f049b4ee30bfbab2d1c1a10c02af904df9fbb /docs/api/swagger.yaml | |
| parent | [docs] Rework README a bit, import into docs (#3006) (diff) | |
| download | gotosocial-b789fe2bc72a1b1bca50da498ae22c10a4e7acc2.tar.xz | |
[feature] filter API v2: Restore keywords_attributes and statuses_attributes (#2995)
These filter API v2 features were cut late in development because the form encoding version is hard to implement correctly and because I thought no clients actually used `keywords_attributes`. Unfortunately, Phanpy does use `keywords_attributes`.
Diffstat (limited to 'docs/api/swagger.yaml')
| -rw-r--r-- | docs/api/swagger.yaml | 42 |
1 files changed, 42 insertions, 0 deletions
diff --git a/docs/api/swagger.yaml b/docs/api/swagger.yaml index 3f14e41e5..46ed95c82 100644 --- a/docs/api/swagger.yaml +++ b/docs/api/swagger.yaml @@ -9245,6 +9245,27 @@ paths: in: formData name: filter_action type: string + - collectionFormat: multi + description: Keywords to be added (if not using id param) or updated (if using id param). + in: formData + items: + type: string + name: keywords_attributes[][keyword] + type: array + - collectionFormat: multi + description: Should each keyword consider word boundaries? + in: formData + items: + type: boolean + name: keywords_attributes[][whole_word] + type: array + - collectionFormat: multi + description: Statuses to be added to the filter. + in: formData + items: + type: string + name: statuses_attributes[][status_id] + type: array produces: - application/json responses: @@ -9361,6 +9382,27 @@ paths: required: true type: string - collectionFormat: multi + description: Keywords to be added to the created filter. + in: formData + items: + type: string + name: keywords_attributes[][keyword] + type: array + - collectionFormat: multi + description: Should each keyword consider word boundaries? + in: formData + items: + type: boolean + name: keywords_attributes[][whole_word] + type: array + - collectionFormat: multi + description: Statuses to be added to the newly created filter. + in: formData + items: + type: string + name: statuses_attributes[][status_id] + type: array + - collectionFormat: multi description: |- The contexts in which the filter should be applied. |