Ronnie Overby

@QuintinWillison @dsherret Here's how I disabled the behavior: ```C# public static JsonSerializerOptions IgnoreCSharpRequiredModifiers(this JsonSerializerOptions options) { options.TypeInfoResolver ??= new DefaultJsonTypeInfoResolver(); options.TypeInfoResolver = options.TypeInfoResolver.WithAddedModifier(static typeInfo => typeInfo.IgnoreCSharpRequiredModifiers()); return options; } private...

the code in this fix actually comes from the upstream repo: https://github.com/langjt/node-http-proxy-json/commit/2a7dee1b8528cd6184528a199a25bb93da787102

Looks like Clutch may be unnecessary for EF 6: http://msdn.microsoft.com/en-US/data/dn469464

I kind of sense this practice falling out of vogue. It doesn't _seem_ to matter as much as it did in the early days of TPL / async / await....