XML and JSON endpoints while forcing Content-Type Text/Plain instead of allowing Web API to handle the serialisation. The f were these devs thinking.

cuz why not lol

Good luck maintaining that :\

@gitpush About to start rewriting it - its an utter mess.

@delegate212

it sure is lol, at least at least if they want both json and xml, read the content type header instead of maintaining two functions :\

@gitpush Its pretty funny tbf they've actually had to go to the length of writing a custom media formatter to force text/plain.

@delegate212 oh I missed that, who the fuck force text/plain... wow, good luck :\

@gitpush Indeed absolute crazy. The responses from the endpoints aren’t consistent some times you’ll get XML, JSON or just random strings. They rely heavily on adding custom headers to most of the responses when in reality it should be in the body.

@delegate212 just rewrite this thing from scratch don't see any hope for it to be fixed lol

Yo Dawg, we heard you like JSON, so we put some JSON in your JSON, so you can deserialize while you deserialize!