Cryptobox serializer should be configurable #915
The hooks to allow use of a configurable serializer are there, but it is hard-coded to "json" currently.
We should support all serializers that we support at the transport level.
Another question is what default cryptobox serializer to use when none was specified. And also how to let the user configure the cryptobox serializer if it shouldn't use the default one.
The text was updated successfully, but these errors were encountered: