Reading Invalid JSON with System.Text.Json

[@coffeeandloot8216]

Thanks for the video, I think this makes it easier to avoid exceptions and improves reliability.

[@robl39]

It will be an uphill battle to get people off of Newtonsoft LOL

[@talwald1680]

Is there an option for treating single quotes as double quotes for property names, or other string values? (I have seen this in the wild and had to resort to string.Replace...)

[@pesfan6385]

In a post api I send {"quantity":"xyz","name":"peter"} and the request are null , the quantity type is decimal i cannot validate with fluentValidator , some idea?

[@PankajNikam]

I wonder if there are any performance impacts when turning off the strict checking.

[@enriquebenedicto9429]

Given the apparent long list of possible options, it seems one would already have to know which options would be realistic candidates in a given environment. This leads me to think that an app reading the json file would be somewhat aware/knowledgeable of where the data comes from, and what format it can typically come in. One can't possibly anticipate ahead of time all the ways a json file might be wrongfully formatted. Also, are there ways to specify what the "comment" formats are? In this example, it was using c/c++ format by default, it seems. But what if semi-columns are used, for instance?

[@pesfan6385]

What happen if i send string in a int value in that json ?

[@foro1]

How to force this to be default for webapis ?

[@jd31068]

This guy James sounds a lot like that long haired bearded guy from the MAUI videos 😉

[@SergioBarrionuevo]

yeah right! hehe

[@julian_b]

I thought the original intention of System.Text.Json was to strictly adhere to the JSON standards?

[@coffeeandloot8216]

It does, the options allow for bending the rules when you need to.

[@robl39]

The intent was to create a highly performant, low memory footprint JSON serializer