feat: add support for deserializing strings as byte arrays #148
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This should resolve #138 as well I think. |
rjzak
force-pushed
the
feat/string-byte-array
branch
from
c8a634a to
ebc9229
Compare
npmccallum
force-pushed
the
feat/string-byte-array
branch
from
ebc9229 to
486741b
Compare
|
@laptou Please fix your git signoff. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ciboriumcurrently does not allow you to deserialize a string as a byte slice or byte array. This breaks the ability to deserialize types likejiff::Timestamp, which prefer to do things this way.