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 public properties to have same JSON attributes #1112

Merged
merged 11 commits into from
Jan 21, 2020

Conversation

j82w
Copy link
Contributor

@j82w j82w commented Dec 19, 2019

Pull Request Template

Description

This fixes all the public properties to have the same JSON attributes for the same public property like etag.

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

Closing issues

closes #1111

…system types. PermissionProperties is now modified to be nullable to match the rest of the resource types.
@j82w j82w added bug Something isn't working breaking non-additive functional behavior changes labels Dec 19, 2019
@j82w j82w requested a review from kirillg as a code owner December 19, 2019 13:47
@j82w j82w self-assigned this Dec 19, 2019
@j82w j82w changed the title Fixed last modified type and public properties to have same JSON attributes Fixed public properties to have same JSON attributes Dec 19, 2019
@j82w j82w removed the breaking non-additive functional behavior changes label Dec 19, 2019
@@ -35,23 +35,23 @@ public class ThroughputProperties
/// <remarks>
/// ETags are used for concurrency checking when updating resources.
/// </remarks>
[JsonProperty(PropertyName = Constants.Properties.ETag)]
[JsonProperty(PropertyName = Constants.Properties.ETag, NullValueHandling = NullValueHandling.Ignore)]
Copy link
Member

Choose a reason for hiding this comment

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

Is this breaking today? or what's the reason to add the NullValueHandling?

Copy link
Contributor Author

@j82w j82w Dec 19, 2019

Choose a reason for hiding this comment

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

Half of the properties have the ignore the other don't. It seems like making it consistent between all the types was missed. Serializing a null _etag or other system properties and sending it to the backend only increase payload size and has no benefit.

kirillg
kirillg previously approved these changes Jan 21, 2020
@j82w j82w dismissed stale reviews from kirillg and kirankumarkolli via c43f9f7 January 21, 2020 12:35
ealsur
ealsur previously approved these changes Jan 21, 2020
@j82w j82w merged commit e3e959d into master Jan 21, 2020
@j82w j82w deleted the users/jawilley/bug/lastmodifiedtime branch January 21, 2020 18:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix LastModified type
4 participants