We have moved to GitHub Issues
Created by Shannon Deminick 20 Jun 2016, 13:35:17 Updated by Warren Buckley 22 Jun 2016, 12:26:47Tags: Unscheduled
Relates to: U4-8606
The reason this happens is because we are not replacing the default formatter, we are modifying it and it is still the instance of the global one, so when it executes it means that the globa json formatter is changed.
see rev: bc2b9ab29850e6473f7c7b6724a5f0e9e1e7a563
@Shandem can you expand details on this please for me to understand the original problem & the fix or alternatively what to test.
The code before was modifying the 'global' JsonFormatter directly:
controllerSettings.Formatters.JsonFormatter.SerializerSettings instead of replacing it so that it is only configured per controller. This means that as soon as this formatter executed, that all JsonFormatter's would have the camel case serializer applied.
kind of hard to test but you could:
OK understand the problem & the code change makes sense, will mark as fixed @Shandem
Backwards Compatible: True
Due in version: 7.5.0
Sprint: Sprint 36