We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This create is just what I need for use with serde_json.
Unfortunately, it doubles the length of all arrays when used with bincode, etc.
Is there a way of ignoring serde-hex for bincode serialisation, while keeping it for serde_json?
The text was updated successfully, but these errors were encountered:
https://stackoverflow.com/questions/67145666/make-serde-only-produce-hex-strings-for-human-readable-serialiser
Sorry, something went wrong.
I notice that secp256k1 uses d.is_human_readable().
d.is_human_readable()
No branches or pull requests
This create is just what I need for use with serde_json.
Unfortunately, it doubles the length of all arrays when used with bincode, etc.
Is there a way of ignoring serde-hex for bincode serialisation, while keeping it for serde_json?
The text was updated successfully, but these errors were encountered: