11 references to AllowNamedFloatingPointLiterals
Microsoft.AspNetCore.Grpc.JsonTranscoding (1)
Internal\Json\JsonConverterHelper.cs (1)
47NumberHandling = JsonNumberHandling.AllowNamedFloatingPointLiterals,
Microsoft.AspNetCore.OpenApi (1)
Schemas\JsonSchemaMapper\JsonSchemaMapper.cs (1)
356else if (numberHandling is JsonNumberHandling.AllowNamedFloatingPointLiterals && simpleTypeInfo.IsIeeeFloatingPoint)
System.Text.Json (9)
src\libraries\System.Text.Json\Common\JsonHelpers.cs (1)
48? (handling.Value & (JsonNumberHandling.WriteAsString | JsonNumberHandling.AllowNamedFloatingPointLiterals)) != 0
src\libraries\System.Text.Json\Common\JsonNumberHandling.cs (1)
9/// The behavior of <see cref="WriteAsString"/> and <see cref="AllowNamedFloatingPointLiterals"/> is not defined by the JSON specification. Altering the default number handling can potentially produce JSON that cannot be parsed by other JSON implementations.
System\Text\Json\Serialization\Converters\Value\DoubleConverter.cs (2)
44else if ((JsonNumberHandling.AllowNamedFloatingPointLiterals & handling) != 0) 59else if ((JsonNumberHandling.AllowNamedFloatingPointLiterals & handling) != 0)
System\Text\Json\Serialization\Converters\Value\HalfConverter.cs (2)
104else if ((JsonNumberHandling.AllowNamedFloatingPointLiterals & handling) != 0) 136else if ((JsonNumberHandling.AllowNamedFloatingPointLiterals & handling) != 0)
System\Text\Json\Serialization\Converters\Value\SingleConverter.cs (2)
45else if ((JsonNumberHandling.AllowNamedFloatingPointLiterals & handling) != 0) 60else if ((JsonNumberHandling.AllowNamedFloatingPointLiterals & handling) != 0)
System\Text\Json\Serialization\JsonSerializer.Helpers.cs (1)
90JsonNumberHandling.AllowNamedFloatingPointLiterals));