Is your feature request related to a problem? Please describe.
It's a painpoint of the API that when you want to edit a user you must first fetch it completely and send that body in your request.
Describe the solution you'd like
Ability to edit a user overwriting/merging just the data you send. On this note of "overwriting/merging" it would be helpful if when you send lists or attribs properties that they are merged rather than overwritten. It might be nice to also be able to specificy this behaviour as a request property, something like mode: "overwrite" | "merge".
+1 to above
And to be able to do this using the email as ID instead of capturing the ID first will also help to have a form that one user can send twice and just update their information.
Is your feature request related to a problem? Please describe. It's a painpoint of the API that when you want to edit a user you must first fetch it completely and send that body in your request.
Describe the solution you'd like
Ability to edit a user overwriting/merging just the data you send. On this note of "overwriting/merging" it would be helpful if when you send
lists
orattribs
properties that they are merged rather than overwritten. It might be nice to also be able to specificy this behaviour as a request property, something likemode: "overwrite" | "merge"
.The only reference I can find is here but nothing seems to have come from it: https://github.com/knadh/listmonk/issues/995#issuecomment-1287776197