[tufaceous-lib] make DeserializedManifest public and serializable, fix serialization #4781
Conversation
This file contains 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
Created using spr 1.3.5
Created using spr 1.3.5
sunshowers
deleted the
sunshowers/spr/tufaceous-lib-make-deserializedmanifest-public-and-serializable-fix-serialization
branch
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.
This is prep work for #4690. I'd like to add support for making changes to a
DeserializedManifest, then serializing it.
However, it turned out that the bytesize crate does not serialize bytes
correctly (bytesize-rs/bytesize#40). To address this,
just use a u64 and write our own deserializer, using the alternative parse-size
crate.
Also add a test to ensure that serialization of the fake manifest roundtrips
correctly.