From 99fdd837c4b320e8bf7d91226e434330530cfc9e Mon Sep 17 00:00:00 2001 From: Genevieve Warren <24882762+gewarren@users.noreply.github.com> Date: Wed, 21 Oct 2020 11:06:49 -0700 Subject: [PATCH] display type with name for xrefs: --- .../5.0/jsonserializer-allows-reading-numbers-as-strings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/includes/core-changes/serialization/5.0/jsonserializer-allows-reading-numbers-as-strings.md b/includes/core-changes/serialization/5.0/jsonserializer-allows-reading-numbers-as-strings.md index 9c159ceb5466d..be4fe8eba0af7 100644 --- a/includes/core-changes/serialization/5.0/jsonserializer-allows-reading-numbers-as-strings.md +++ b/includes/core-changes/serialization/5.0/jsonserializer-allows-reading-numbers-as-strings.md @@ -12,7 +12,7 @@ Starting in .NET 5.0, quoted numbers in JSON payloads are considered valid, by d > > - There is no behavior change for the default, standalone or . > - This is technically not a breaking change, since it makes a scenario more permissive instead of more restrictive (that is, it succeeds in coercing a number from a JSON string instead of throwing an exception). However, since this is a significant behavioral change that affects many ASP.NET Core apps, it is documented here. -> - The and extension methods also use the set of serialization options. +> - The and extension methods also use the set of serialization options. #### Version introduced