Upgrade plist to 0.3 and take advantage of serde integration #181
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
cmyr
reviewed
Jun 28, 2018
| Plist::Integer(value) => Settings::Number(value.into()), | ||
| Plist::String(s) => Settings::String(s), | ||
| } | ||
| let settings = deserialize(reader)?; |
There was a problem hiding this comment.
or just:
Ok(deserialize(reader)?)(okay either way obviously, just riffing)
There was a problem hiding this comment.
Yeah, had that before, but then decided that having an extra variable reads a bit nicer because it removes the )?) 🤷♂️.
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.
I noticed that plist comes with serde integration now, so we can just directly deserialize into the serde_json Value types using the magic of serde :).
Output of
cargo update: