This addresses an issue when consuming the bindle crate in WAGI (and, no doubt, other applications): the ed25519_dalek::Signature::from_bytes, used in invoice/signature.rs and invoice/verification.rs, method is actually on the signature::Signature trait which is not in scope in those files. I don't yet understand why those files would compile in the Bindle client and server, but they don't compile in WAGI. And adding the trait to the files makes them give an "unused import" warning in Bindle!
The fix is to instead use Signature's TryFrom implementation, which is documented in the Signature examples, doesn't need to be brought into scope, and delegates directly to from_bytes so shouldn't change any behaviour #famouslastwords.
@vdice would be great if you could give this a test please - I'm not sure how to exercise the signature stuff. Thanks!
This addresses an issue when consuming the
bindle
crate in WAGI (and, no doubt, other applications): theed25519_dalek::Signature::from_bytes
, used ininvoice/signature.rs
andinvoice/verification.rs
, method is actually on thesignature::Signature
trait which is not in scope in those files. I don't yet understand why those files would compile in the Bindle client and server, but they don't compile in WAGI. And adding the trait to the files makes them give an "unused import" warning in Bindle!The fix is to instead use Signature's
TryFrom
implementation, which is documented in the Signature examples, doesn't need to be brought into scope, and delegates directly tofrom_bytes
so shouldn't change any behaviour #famouslastwords.@vdice would be great if you could give this a test please - I'm not sure how to exercise the signature stuff. Thanks!