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

Implement asynchronous support in ODataJsonLightParameterDeserializer #2311

Conversation

gathogojr
Copy link
Contributor

@gathogojr gathogojr commented Feb 8, 2022

Issues

This pull request partially fulfills #2019.

Description

Implement asynchronous support in ODataJsonLightParameterDeserializer.

Checklist (Uncheck if it is not completed)

  • Test cases added
  • Build and test with one-click build and test script passed

Additional work necessary

If documentation update is needed, please add "Docs Needed" label to the issue and provide details about the required document change in the issue.

@gathogojr gathogojr marked this pull request as draft February 8, 2022 04:26
@gathogojr gathogojr force-pushed the feature/odatajsonlightparameterdeserializer-async branch from 5e2a6f1 to 6603b5e Compare February 8, 2022 07:33
@gathogojr gathogojr marked this pull request as ready for review February 8, 2022 07:33
public async Task ReadPrimitiveParameterAsync()
{
var payload = "{\"rating\":4}";
var setRatingAction = new EdmAction("NS", "SetRating", null);
Copy link
Member

@marabooy marabooy Feb 8, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Move this closer to usage for consistency.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

await this.ProcessPropertyAsync(
propertyAndAnnotationCollector,
propertyAnnotationValueReaderAsync,
async (propertyParsingResult, parameterName) =>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A good candidate for a future update on this lambda so it captures less items. 😄

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I plan to tackle in a separate to address the same concern in related PRs

@gathogojr gathogojr force-pushed the feature/odatajsonlightparameterdeserializer-async branch 3 times, most recently from 08a5656 to 8546f08 Compare February 11, 2022 19:38
@@ -25,6 +26,11 @@ internal sealed class ODataJsonLightParameterDeserializer : ODataJsonLightProper
private static readonly Func<string, object> propertyAnnotationValueReader =
annotationName => { throw new ODataException(ODataErrorStrings.ODataJsonLightParameterDeserializer_PropertyAnnotationForParameters); };

/// <summary>OData property annotation asynchronous reader for parameter payloads.</summary>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this statement is necessary here. Its contradicting the second statement. You can get rid of this and just leave the second one.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed by moving the statement about ODataJsonLightParameterDeserializer not supporting reading of property annotations to the body of the delegate

@gathogojr gathogojr force-pushed the feature/odatajsonlightparameterdeserializer-async branch from 8546f08 to 66b8565 Compare February 14, 2022 08:16
Copy link
Contributor

@KenitoInc KenitoInc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved with minor comments

Debug.Assert(propertyAndAnnotationCollector != null, "propertyAndAnnotationCollector != null");
this.AssertJsonCondition(JsonNodeType.Property, JsonNodeType.EndObject);

bool parameterRead = false;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
bool parameterRead = false;
bool parameterRead = false;


ODataParameterReaderState state;
object parameterValue;
EdmTypeKind parameterTypeKind = parameterTypeReference.TypeKind();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
EdmTypeKind parameterTypeKind = parameterTypeReference.TypeKind();
EdmTypeKind parameterTypeKind = parameterTypeReference.TypeKind();

switch (parameterTypeKind)
{
case EdmTypeKind.Primitive:
IEdmPrimitiveTypeReference primitiveTypeReference = parameterTypeReference.AsPrimitive();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
IEdmPrimitiveTypeReference primitiveTypeReference = parameterTypeReference.AsPrimitive();
IEdmPrimitiveTypeReference primitiveTypeReference = parameterTypeReference.AsPrimitive();

@gathogojr gathogojr force-pushed the feature/odatajsonlightparameterdeserializer-async branch from 66b8565 to ce8f2c6 Compare February 14, 2022 08:48
@pull-request-quantifier-deprecated

This PR has 371 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Large
Size       : +371 -0
Percentile : 77.1%

Total files changed: 4

Change summary by file extension:
.cs : +371 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detetcted.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@gathogojr gathogojr merged commit 9770082 into OData:master Feb 14, 2022
@gathogojr gathogojr deleted the feature/odatajsonlightparameterdeserializer-async branch February 14, 2022 09:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants