mirror of
https://github.com/superseriousbusiness/gotosocial.git
synced 2025-10-29 01:02:25 -05:00
[feature] Implement CSV import for mutes (#3696)
* Implement CSV import for mutes * update swagger.yaml * update documentation * add ImportTestSuite.TestImportMutes * fix comment typo
This commit is contained in:
parent
d73acc70d5
commit
0118e03cda
7 changed files with 349 additions and 1 deletions
|
|
@ -8403,7 +8403,7 @@ paths:
|
|||
type: file
|
||||
- description: |-
|
||||
Type of entries contained in the data file:
|
||||
- `following` - accounts to follow. - `blocks` - accounts to block.
|
||||
- `following` - accounts to follow. - `blocks` - accounts to block. - `mutes` - accounts to mute.
|
||||
in: formData
|
||||
name: type
|
||||
required: true
|
||||
|
|
|
|||
|
|
@ -266,3 +266,6 @@ Both merge and overwrite operations are idempotent, which basically means that d
|
|||
|
||||
!!! info
|
||||
For a variety of reasons, it will not always be possible to recreate every entry in an uploaded CSV file via importing. For example, say you are trying to import a CSV of follows containing `example_account`, but `example_account`'s instance has gone offline, or their instance blocks yours, or your instance blocks theirs, etc. In this case, the follow of `example_account` would not be created.
|
||||
|
||||
!!! warning
|
||||
The CSV format for mutes does not contain expiration data, so temporary mutes are exported (and imported) as permanent mutes.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue