Extend usage of name converter

[jderusse]

Actualy name converter is used in (de)normalization of the object.
But it should also be used in several locations:

• In violation's propertyPath

"violations": [
        {
            "message": "This value should not be blank.", 
            "propertyPath": "content" <== here
        }
    ]

• In filters => http://localhost:8000/api/offers?price=10 price should be denormalized
• or in /offers?order[name]=desc&order[id]=asc.

[dunglas]

Also in EntrypointBuilder and in ApiDocumentationBuilder.

[Simperfit]

What is this about ? Is it still relevant ?

[dunglas]

It has been partially fixed by @meyerbaptiste in #770 but I think there are still some places to cover like property paths and filters.

[aistis-]

The issue still persist in v2.0.3

I use config:

api_platform:
    name_converter: 'serializer.name_converter.camel_case_to_snake_case'

An example of returned 400 response:

{
	"type": "https://tools.ietf.org/html/rfc2616#section-10",
	"title": "An error occurred",
	"detail": "categoryId: This value should not be blank. supplierId: This value should not be blank. value: This value should not be blank.",
	"violations":
	[
		{
			"propertyPath": "categoryId",
			"message": "This value should not be blank."
		},
		{
			"propertyPath": "supplierId",
			"message": "This value should not be blank."
		},
		{
			"propertyPath": "value",
			"message": "This value should not be blank."
		}
	],
}

Neither propertyPath nor categoryId/supplierId is run over name converter.

[Simperfit]

This has been fixed by @meyerbaptiste