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

[release/6.0] Fix System.Object serialization with custom number handling #62193

Merged
merged 3 commits into from
Jan 8, 2022

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Nov 30, 2021

Backport of #62020 to release/6.0

/cc @eiriktsarpalis

Customer Impact

Addresses a customer-reported regression concerning serialization of new object() instances when used in conjunction with custom number handling. The regression was introduced by #54436 which refactored polymorphic serialization for object types but failed to account for custom number handling.

Testing

Added regression tests that check for polymorphic serialization in custom number handling scenaria.

Risk

Low. This change impacts a rare corner case (serializing new object() instances).

@ghost
Copy link

ghost commented Nov 30, 2021

Tagging subscribers to this area: @dotnet/area-system-text-json
See info in area-owners.md if you want to be subscribed.

Issue Details

Backport of #62020 to release/6.0

/cc @eiriktsarpalis

Customer Impact

Testing

Risk

Author: github-actions[bot]
Assignees: -
Labels:

area-System.Text.Json

Milestone: -

@eiriktsarpalis eiriktsarpalis added this to the 6.0.x milestone Nov 30, 2021
@eiriktsarpalis eiriktsarpalis added the Servicing-consider Issue for next servicing release review label Nov 30, 2021
@eiriktsarpalis eiriktsarpalis self-assigned this Nov 30, 2021
@eiriktsarpalis
Copy link
Member

Servicing approved over email.

@eiriktsarpalis eiriktsarpalis added api-approved API was approved in API review, it can be implemented Servicing-approved Approved for servicing release NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) and removed Servicing-consider Issue for next servicing release review api-approved API was approved in API review, it can be implemented labels Dec 1, 2021
@safern safern removed the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Dec 15, 2021
@safern
Copy link
Member

safern commented Dec 15, 2021

Closing and reopening to trigger CI again.

@safern safern closed this Dec 15, 2021
@safern safern reopened this Dec 15, 2021
@danmoseley
Copy link
Member

@eiriktsarpalis @ericstj do we need to address feedback here before 6.0.2 cutoff?

@ericstj
Copy link
Member

ericstj commented Jan 7, 2022

Sure, I can help with that since @eiriktsarpalis is out.

@ericstj
Copy link
Member

ericstj commented Jan 7, 2022

Failing tests:
#63521
#63523
#63522
#58927

@safern safern merged commit abe7d08 into release/6.0 Jan 8, 2022
@safern safern deleted the backport/pr-62020-to-release/6.0 branch January 8, 2022 01:01
@ghost ghost locked as resolved and limited conversation to collaborators Feb 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Text.Json Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants