Manuel Mauro
Manuel Mauro
It seems like a good idea!
This solution would be ideal also in case we would like to add some higher level features to algonaut. In particular, I was thinking of crates for [ARC3 (NFTs)](https://github.com/algorandfoundation/ARCs/blob/main/ARCs/arc-0003.md) or...
The project on which `algonaut` is based used to integrate the Algorand's SDK cucumber test suite, you can take a look at it here: https://github.com/mraof/rust-algorand-sdk/tree/master/tests It has been removed to...
Let's comply with the docs then!
It seems like a good solution to me, while I find the current organization ambiguous.
Hi! I thought that instead of adding tests we can use this reference implementation https://github.com/manuelmauro/algorand-oas-generated-v2-clients
@i-schuetz do you have any idea about this? I am thinking that the crate `algonaut_client` might stay very low-level with functions almost 1-to-1 with Algorand's API, while improving the ergonomics...
Great, seems a good solution! I only have mixed feelings on builders' naming convention. I noticed that `reqwest` follows this convention while crates like `actix` seems not to.
@Niceural Actually no, we are still using `u64`.
I am taking a look at this and came up with the following ```rust pub struct MiddlewareStack { middlewares: Vec, } impl MiddlewareStack { pub fn new() -> MiddlewareStack {...