Query : Fixes LINQ Serialization CamelCase Naming Policy #4253
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Maya-Painter
requested review from
FabianMeiswinkel,
adityasa,
ealsur,
khdang,
kirankumarkolli,
kirillg,
neildsh and
sboshra
as code owners
kirankumarkolli
approved these changes
Apr 23, 2024
adityasa
reviewed
May 1, 2024
...TestBaseline/LinqTranslationWithCustomSerializerBaseline.TestMemberInitializerDataMember.xml
Show resolved
Hide resolved
This was referenced Jul 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
As it stands now, if the CamelCase naming policy is specified on the CosmosLinqSerializerOptions it will not be applied to all LINQ translations.
This PR fixes this bug so that the naming policy is applied in all scenarios. This will change the expected (incorrect) behavior.
Type of change