Nutomic
See https://github.com/LemmyNet/lemmy/pull/4580 for an example how to implement this.
When doing this I would change the endpoint to `/api/v4/person/list` with parameter `banned_only`. It only requires slightly more work, fulfills the same purpose and can later be extended with more...
I dont see any reason why banned users should be a separate endpoint, its better to do like [GetPosts](https://github.com/LemmyNet/lemmy/blob/main/crates/api_common/src/post.rs#L83) with various filters (banned_only, local_only etc). This has been frequently requested...
The mentioned test is [here](https://github.com/LemmyNet/lemmy/blob/main/crates/db_schema_file/src/schema_setup.rs#L339). Implementing this would work more or less so: - Set `Options.limit` to only run the first few migrations (enough to create tables for user, community,...
Not sure what you mean, but its better to keep things simple and avoid unnecessary complexity.
Its enough to check after all migrations are finished that the test data still exists.
Right then you also have to use raw sql to validate data after migrations.
@informapirata #5257 will be released as part of Lemmy 1.0. The changes are too big to backport for 0.19.
Votes can also be deleted directly in the database. I dont know of any case where that was needed, so implementing a special feature seems unnecessary.
Yes this would be federated together with the removal action.