Closed UkoeHB closed 5 months ago
I should probably get rid of WebServerDestinationSerializable
and just implement Serialize/Deserialize manually. Let's see if the changes are worthwhile first.
Hey, thanks for the followup, it's late for me so I don't have time to look too much, I'll review and test the changes tomorrow and I'll also respond to #12 tomorrow.
Quickly though, one thing I noticed is that you could use the serde feature on rust_url directly instead of using the serializable dest struct, it would save you having to implement the serialization:
url = { version = "2.4", optional = true, features = ["serde"] }
Quickly though, one thing I noticed is that you could use the serde feature on rust_url directly instead of using the serializable dest struct, it would save you having to implement the serialization: url = { version = "2.4", optional = true, features = ["serde"] }
Thanks for pointing this out. One additional problem is Serialize/Deserialize aren't implemented for SocketAddr
.
Quickly though, one thing I noticed is that you could use the serde feature on rust_url directly instead of using the serializable dest struct, it would save you having to implement the serialization: url = { version = "2.4", optional = true, features = ["serde"] }
Thanks for pointing this out. One additional problem is Serialize/Deserialize aren't implemented for
SocketAddr
.
Yes they are I believe, SocketAddr is one of the types listed in the docs of serde::ser
Reference. @jwric can you test these changes?
Closes #12.