Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed LINQ with camel case. #909

Merged
merged 2 commits into from
Oct 15, 2019
Merged

Conversation

j82w
Copy link
Contributor

@j82w j82w commented Oct 14, 2019

Pull Request Template

Description

Camel case with LINQ was not being tested because of a missing tag in the test. LINQ was not honoring camel case because the serialization settings did not get passed to the inner method. I removed all the default nulls to avoid the missing parameter in the future.

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

fixes #905

khdang
khdang previously approved these changes Oct 14, 2019
simplynaveen20
simplynaveen20 previously approved these changes Oct 14, 2019
@j82w j82w self-assigned this Oct 15, 2019
@j82w j82w dismissed stale reviews from kirankumarkolli, simplynaveen20, and khdang via e76c5e9 October 15, 2019 13:30
@j82w
Copy link
Contributor Author

j82w commented Oct 15, 2019

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@j82w j82w merged commit f625dbd into master Oct 15, 2019
@j82w j82w deleted the users/jawilley/linq/camal_case_fix branch October 15, 2019 19:20
j82w added a commit that referenced this pull request Oct 15, 2019
* Fixed linq with camel case.

* Updated changelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

LINQ Provider does not accept PropertyNamingPolicy setting
5 participants