Jonas Hedman Engström
Jonas Hedman Engström
Are there any updates on whether this might be supported in v2? I couldn't find any reference of it when looking at the tracking issue. Thanks!
It's a major stability- and security-concern for us to have this functionality compiled into production code and/or our build pipeline. We're maintaining a quite strict [`cargo deny`](https://github.com/EmbarkStudios/cargo-deny) config to make...
Not embedding the payload on 5XX responses makes sense but it would be nice to have a default handler for the other error responses. I'm not sure how to decide...
Pretty much, I think. But it should simply drop the unknown char `to_string_lossy_impl(rest, acc "�")` -> `to_string_lossy_impl(rest, acc)` *Edit*: Nevermind.. Yes, it should not just drop the codepoint, a mapping...
Huh, alright! Maybe I just never hit that place in the code then when running on earlier versions? I was using it in a "shared" lib used on both targets....
Feel free to close this. Sorry for the noise!
Cool! Yeah, I was planning to take a stab at implementing #80 if/when I get some time over. I'll look into adding some tests soon