Validation error output about validator HOT 5 CLOSED

I prefer first way with additional parameter in Result::getAttributeErrorMessagesIndexedByPath() and
Result::getErrorMessagesIndexedByPath() and by default escape separator chars in value path elements. It's allow to consumers correctly parse result keys.

from validator.

What is your use case for this method?

from validator.

@arogachev,

I have REST API. After validating the data with this method, I get all the errors given their path, since I'm using a Nested validator. Then I generate an exception, where I put the received array of errors, encode it through json_encode and give it to the client. And as planned, the key in this array can look like: "account.profile.name".

Also, "account.profile.name" is the key in the array of data that comes from the client to the server and it sends them for validation. Therefore, in order to avoid the behavior that Nested validator has, when "sub-arrays" are formed from such keys, I follow the documentation and escape the dots. "account/.profile/.name".

If a key contains the separator (.), or Each shortcut (*), it must be escaped with backslash () in the rule config to work correctly. In the input data escaping is not needed.

If the "account.profile.name" attribute fails validation, then I would expect to see the following in the response from the getErrorMessagesIndexedByPath: {"account.profile.name": "error text"},
but not {"account//.profile//.name": "error text"}

from validator.

I hope you got what I meant :)

from validator.

Makes sense. Thanks for suggestion, @bouledepate

from validator.