Hugo
Hugo
@jbencin-stacks Let's create a new one and close this one. So that you can fully own it It was created with my personal account anyway.
@brice-stacks I'd love to have your opinion regarding https://github.com/stx-labs/clarinet/issues/2022
Also, we could adopt the leading `_` convention for "allowed unused code"
Thanks @jbencin
Hello @grandima Have you seen the review? Thank you
@aaronb-stacks Historically, we used to `develop` so that we could easily satisfy the dependencies of both the chainhook repo and the clarinet repo, without needing to make synced PRs on...
Hey @emmanuelist Thanks for your contribution. This is a step in the right direction. But maybe still not ideal. Regarding the messages: "use of unresolved contract" is often related to...
@BowTiedRadone The contract interface you get in Clarinet is implemented upstream in stacks-core. This is basically the same thing that what the API returns as well (eg: https://api.hiro.so/v2/contracts/interface/SP4SZE494VC2YC5JYG7AYFQ44F5Q4PYV7DVMDPBG/stacking-dao-core-btc-v3) We'll likely...
> we don’t even know the trait name since the interface only gives us something like arg_name: "trait_reference" Ok, I see. Indeed, `"type": "trait_reference"` isn't super helpful. I'll try to...
Yes, I get it. Just trying to keep this issue focused on 1 issue / pain point. To me, this problem: > would it be possible to add a method...