Skip to content

Conversation

@flobernd
Copy link
Member

Configure DefaultFieldNameInferrer to use JsonSerializerOptions.PropertyNamingPolicy, if the DefaultSourceSerializer is used.

The other way around is already implemented. If the DefaultSourceSerializer is used and the DefaultFieldNameInferrer is changed, the JsonSerializerOptions.PropertyNamingPolicy gets configured to use a custom PropertyNamingPolicy that applies the DefaultFieldNameInferrer transformations.

Closes #8357

@flobernd flobernd changed the title Synchronize DefaultFieldNameInferrer and PropertyNamingPolicy Synchronize DefaultFieldNameInferrer and JsonSerializerOptions.PropertyNamingPolicy Sep 27, 2024
@flobernd flobernd force-pushed the field-name-inferrer-naming-policy branch from 85d135f to 68e1fed Compare September 27, 2024 09:43
@flobernd flobernd merged commit b077a88 into main Sep 27, 2024
4 of 19 checks passed
@flobernd flobernd deleted the field-name-inferrer-naming-policy branch September 27, 2024 09:46
flobernd added a commit that referenced this pull request Sep 27, 2024
flobernd added a commit that referenced this pull request Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

8.x Relates to a 8.x client version Area: Client Category: Enhancement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PropertyNamingPolicy from JsonSerializerOptions of the DefaultSourceSerializer is not applied for mappings

1 participant