Serialization for networking transportation #2
Description
Currently the unexported error type cannot be serialized because all its fields are unexported.
The problem with this is that the error values doesn't contain any information if it's serialized to be transported through the network and that's a requirement when using this package for services which runs remotely, which are some of the ones which can be enhanced of using error codes.
This is something that I've already known, but I left for the future for:
- releasing the first version without holding it for longer time.
- I want to think deeper in what to serialize.
The goal is that the error values must be able to be serialized and transported from the service to the client and the client must be able to deserialize and get the important information from it.