SaveUserSettings returns "user_already_exists" if you follow docs typings

[nick-delirium]

Method docs shows that almost everything is optional, yet in reality if you don't include the entire object, it will return an error.

Payload:

{ "auth": <jwt token>, "show_nsfw": false }

result: user_already_exists

Payload 2:
{ "show_nsfw": true, "theme": "browser", "default_sort_type": 1, "default_listing_type": 1, "interface_language": "browser", "discussion_languages": [], "avatar": <url>, "banner": null, "display_name": "name", "show_avatars": true, "bot_account": false, "show_bot_accounts": true, "show_scores": true, "show_read_posts": true, "show_new_post_notifs": false, "email": "email", "bio": "**this is** a test", "send_notifications_to_email": false, "matrix_user_id": null, "auth": "<JWT>" }

result:
all good

[nick-delirium]

(btw, why its mixing actual feed/lemmy/client settings with profile information)

[aeharding]

Related: #3565

[dessalines]

Stale issue, feel free to reopen if its still a problem.

[TheBrokenRail]

This issue is absolutely still a problem. On https://voyager.lemmy.ml, sending a SaveUserSettings with only one property set will give a {"error":"user_already_exists"} response.