Usage of alternative (JSON / De-)Serializers

[joergbattermann]

Good morning,

I just started playing with refit and I was wondering whether it was possible to use an alternative Json serializer and deserializer than Json.Net? As far as I can see it its hard-wired mostly in RequestBuilderImplementation.cs, but I've come to love Jil, been using NetJson in another project and some might use protobuf, MessagePack or some other formats.

While those might not provide support for the exact same amount of platforms as refit does, it might be nice to have a choice and I was wondering, whether the hard-coded usage of Json.net could be de-coupled and one could provide custom (de)serialization providers for refit?

Basically something like providing a Serializer registration point in https://github.com/paulcbetts/refit/blob/master/Refit/RefitSettings.cs, use that one instead of Json.Net directly?

I've forked away refit and started dabbling with this idea but wanted to check upfront whether this is something you might be ok with?

Cheers,
-J

[clairernovotny]

This is likely in-line with #75, so from a generic standpoint the thinking seems to be more about providing a custom serialization mechanism of any kind per type/method, etc.

[joergbattermann]

@onovotny Ahh yeah #75 and #83 are exactly what I had in mind. I'll close this issue here, keep an eye on the other two and once these make their way into refit & one can write custom serializers for, I'll do just that.

Thanks for pointing me in the right direction!