With the current bits serializing an ISerializable type would generate json with the backing fields instead of properties.
This is rather the less common use case for web API. Most customers, I assume, would prefer to just serialize public properties instead of the backing fields.
We should change the default behavior and also expose a knob on the Resolver to easily switch it instead of writing a new class.
This is rather the less common use case for web API. Most customers, I assume, would prefer to just serialize public properties instead of the backing fields.
We should change the default behavior and also expose a knob on the Resolver to easily switch it instead of writing a new class.