Make Manifest
and Package
easier to instantiate
#22
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.
Manifest
andPackage
are currently quite annoying to instantiate because all the fields need to be explicitly assigned even if only a small subset is used.This PR implements the
Default
trait for theManifest
struct allowing an instantiation likeManifest { package, ..Default::default() }
.This PR also adds a
new()
fn to thePackage
struct for similar reasons. An alternative to this is implementingDefault
too, but that would leave us withname: ""
andversion: ""
. I'm undecided which way feels better, but fornew()
there is prior art.Finally, this PR also adds a small serialization test case, to ensure that these API keep working in the future :)
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.