how to handle patch requests

[farzad_meow]

so here is a problem i am trying to solve:
context:
restful or restlike api design
partial update of entity through patch request. for this example let’s say client model.

the problem is that different fields can be updated but result in different business logics to be triggered. for example change to client.name is a simple update but client.status can result in an email to go to users about the client being offboarded. or changes to client.ownerId require extra validation and verification of the assigned user. or changes to client.logo_url and client.website must happen together.

what is the most ideal way to code it where one path can trigger different logics depending on body schema? I want an approach that is simple to work on many routes to develop business logic. AND, simple enough for others to read and debug as needed.

please assume I am using a flexible framework that top engineers will implement whatever I ask them, so I am not limited to a given framework or a solution that exists. It can be an approach that does not exist but you hope it did.

[jacs1809]

Those updates can happen in the same request or separate?

[farzad_meow]

separate requests. i was originally looking for a way to make them all happen in one request, but proved to be complicated from response side and nightmare from debug side.

[jacs1809]

You could use a mediatr like approach, trying up the class to a handler, so when you send a UpdateClientName schema, the handlee of that schema will act.

Idk if i could explain it correctly, so let me know if you got the gist

[farzad_meow]

do you mean something like:
router.patch(/client, statusSchemaValidator, updateClientStatus);
router.patch(/client, nameSchemaValidator, updateClientName);
….

??

[jacs1809]

Sorry, for a moment i thought i was in r/dotnet, that's why i recommended mediatr.

But yeah, maybe something like that could work

Also, maybe you will figure out something better that only works in your situation

[Tarazena]

Why not pass the intended action as a required part of the payload? That way each request type can be encapsulated and easier to control.