maybe add the array size likeArray(2) since Object and Resource also add further data

I don't really like that writing, sinceArray(2) is the output ofprint_r when an array contains only the value2 and might cause confusion.

print_r returnsArray ( [0] => 2 )

I still don't see the usefulness of this return value. It should format the value, i.e. the contents, but it basically returns the same asformatTypeOf. It returns the type and not the contents of the array. So it does not add anything new. So ideally it should output a concise representation of the array like['foo', 1, 'Object(Author)']. Or at least the array size as I suggested above.

Imagine the this is used in theCountValidator.

I don't think this valueneeds to be very useful. In most cases, validation messages are displayed to the end user. Displaying something like['foo', 1, 'Object(Author)'] to an average end users frightens them because they think something is broken.

Developers can always call$violation->getInvalidValue() to analyze the value in detail.

Resource ID and object class are also implementation detail not intended for end users.

I agree with both of you@webmozart and@Tobion!

If this is displayed to the end users, we should not be too precise; so the resource id is not needed, but I would even say that displayingarray,object, orresource to the end user looks weird as he probably did not enter that in a form value anyway.

Ok, I will change these outputs to just "array", "object" and "resource" then. I agree that this doesn't help end users very much. I'd even go further to say that messagesshould never include the value if that value is one of these types. If developers choose to include the value in the message anyway, the displayed information will be minimal.

indexing by $key should not be necessary

Can you clarify what you mean?

Nvm, didn't see you replace the interated array values. Maybe using another array like$convertedValues[] = ... would be cleaner.

informatValue the parameter is named$prettyDateTime. Seems incosistent at the moment.

Thanks! Fixed

Could you add some more explanations about when/why/how this is ever called? Something along the lines of:

"This method is used when a constraint error message contains the {{ value }} placeholder. By default, Symfony never includes it, but the developer can override those error messages. It's up to the developer to make sure it actually makes sense to include such string representation of submitted values in error messages."

Done