Thanks for the great library. There is an inconsistency in data serialization when we opt in for CamelCase serialization. Root level properties are serialized as expected but all properties in nested data models are kebab-cased. So it looks like this:
{ "data": { "type": "table-filter", "id": "12", "attributes": { "isDefault": false, "orderBy": { "field-name": "Field2", "is-descending": true }, "where": [ { "field-name": "Field1", "condition": "=", "value": "5" } ] } }, "links": { "self": "http://example.com/api/people/123" } }
The issue can be easily fixed if we pass IPropertyNameConverter (provided in ResourceSerializer) to JsonApiContractResolver.
Hi all,
Thanks for the great library. There is an inconsistency in data serialization when we opt in for CamelCase serialization. Root level properties are serialized as expected but all properties in nested data models are kebab-cased. So it looks like this:
{ "data": { "type": "table-filter", "id": "12", "attributes": { "isDefault": false, "orderBy": { "field-name": "Field2", "is-descending": true }, "where": [ { "field-name": "Field1", "condition": "=", "value": "5" } ] } }, "links": { "self": "http://example.com/api/people/123" } }
The issue can be easily fixed if we pass IPropertyNameConverter (provided in ResourceSerializer) to JsonApiContractResolver.
Thanks!