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

Added specification for field handling #32711

Closed

Conversation

YohDeadfall
Copy link
Contributor

Opening it as work in progress since there should some work be done and the right decision taken about how fields should be handled. After this gets merged I will continue my work on #2192.

Copy link
Contributor

@layomia layomia left a comment

Choose a reason for hiding this comment

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

Please add notes addressing crucial questions for this feature highlighted in #2192 (comment):

  • Which of the existing property-level attributes should be applied to fields? Should JsonExtensionData apply to fields?
  • Which of the options in JsonSerializerOptions should apply to fields? Should PropertyNamingPolicy, PropertyNameCaseInsensitive apply to fields, or do we need new options?
  • Should readonly fields be supported for deserialization? Should there be an option to ignore readonly fields for serialization (an equivalent to IgnoreReadOnlyProperties)?

Everything that comment should be included in this spec, at least as an open question.

@layomia
Copy link
Contributor

layomia commented Apr 6, 2020

Thanks, @YohDeadfall. I've added the API proposal for this feature - #34558.

@layomia layomia closed this Apr 6, 2020
@YohDeadfall YohDeadfall deleted the json-field-support-api branch April 6, 2020 14:41
@ghost ghost locked as resolved and limited conversation to collaborators Dec 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants