This repository was archived by the owner on Mar 23, 2021. It is now read-only.
Second fix of network serialization for serde#1127
Merged
Conversation
Signed-off-by: Philipp Hoenisch <philipp@hoenisch.at>
thomaseizinger
approved these changes
Jul 23, 2019
D4nte
approved these changes
Jul 23, 2019
This was referenced Jul 23, 2019
Open
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Apparently serde and strum are using different ways for serialization, one was configured and one was derived from the enum variant