fixes #580

[mirgil]

[mirgil]

@mirgil please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree

[mirgil]

I believe the protocol expects these to be lower camel case. If so, changing this would be non-compliant.

Which protocol? Serialization should be done according to the JsonSerializerOptions.PropertyNamingPolicy. If no policy is defined, the original property (name and case) should be used.

[gathogojr]

I believe the protocol expects these to be lower camel case. If so, changing this would be non-compliant.

@mikepizzo I might be wrong but I think that the PageResultValueConverter is applicable in non-EDM scenarios - I don't think the items, nextpagelink and count property names used currently have anything to do with OData standard. @xuzhg can correct me if I'm wrong. Be that as it may, this PR has no tests to validate the changes.

Thank you @mirgil for you contribution. Could you please add tests to validate the changes?

[wachugamaina]

Please provide a description of the problem and how this fixes it in the pr description.

[wachugamaina]

Could we have some tests for the new functionality ?