Handle return "validation" errors

[blechatellier]

Is there a method similar to handleReturnedServerError for validation errors? I would like to have a single method to handle both server and validation errors and check for the error type. I'm using zod in other parts of my backend and need to handle that logic in both places otherwise.

I've seen the handleValidationErrorsShape method but I want to set this globally, not on every schema.

[MrOxMasTer]

In fact, I have been suggesting to the author for a very long time to make a validation error handling function, but unfortunately the author of the library ignores me.

#206

I don't remember what I wrote then, but there really isn't enough function like handleServerError

You can call it something like this: handleValidationError

You can also add the second arguments of utils as in handleServerError, so that there would be something to return. And the first argument above is this ve, like 'handleValidationErrorShape'.

This feature can be added both for individual schemes and for the general client

[TheEdoRan]

Hi, the server error shape is a global setting because all the actions share the same returned server error type. However, validation errors are determined by the schema you pass to the action you're defining, that's why it wouldn't make any sense to set an option at the global client level, other than a generic "flattened" | "formatted" default shape. The client is used to define all the actions of your application, there's just no way to know the specific schemas (and so, validation errors types) of all your actions at the top level of the hierarchy, it's impossible. Hope this clears things up!

[MrOxMasTer]

I don't understand what you're trying to say.

Okay, so I thought about it and realized that I can perform actions in case of a validation error, but the problem is that I don't have any contact with the client. If there is a validation error, I cannot return anything additional to the client, except for the validation error itself made by the library, and this is a problem if I want to return, for example, what the user sent or the context to the client in state

I will put this in a separate discussion.

[TheEdoRan]

@MrOxMasTer Ok, it's clearer now. I think I can pass an utils object with additional data (such as clientInput, metadata, ctx, etc.) to handleValidationErrorsShape function, found in schema method (your "variant 1" code snippet).

[MrOxMasTer]

@MrOxMasTer Ok, it's clearer now. I think I can pass an utils object with additional data (such as clientInput, metadata, ctx, etc.) to handleValidationErrorsShape function, found in schema method (your "variant 1" code snippet).

Please read this. That's the problem I'm talking about:
#260

It would be great to make useStateAction, but as I understand it, without changing `react' this will not work

[MrOxMasTer]

@MrOxMasTer Ok, it's clearer now. I think I can pass an utils object with additional data (such as clientInput, metadata, ctx, etc.) to handleValidationErrorsShape function, found in schema method (your "variant 1" code snippet).

so that he supports progressive improvement*

[TheEdoRan]

Starting from v7.9.2, utils object is passed to both handleValidationErrorsShape and handleBindArgsValidationErrorsShape functions as the second argument. (#263)