Hugo C
Hugo C
@lgalabru This is fixed for the clarinet-sdk (#1360, #1437) The issue title also mention `clarity-vsce`, but I don't see what would be the impact of deployment plans in the extension....
@MicaiahReid Could this be linked to #974
Closing this one. If similar issues happen again, I recommend opening a new issue referencing this one to make it easier to track
I'll test if it already works. See with @MicaiahReid about the lcov format compatibility issue
@lgalabru It seems to be working fine (I probably need to test on bigger project). The only requirement would be to rename the lcov file into `lcov.info` (or add the...
This is with the extension you linked. > would it make sense to augment our extension to support this out of the box? Why reinvent the wheel? Or it would...
Totally makes sense. Non exhaustive list of WASM components that could be expose - deployment plan helpers (for the platform) - clarity-events - get contract interface (cf https://github.com/hirosystems/clarinet/issues/913) - lsp...
Sounds like we can tackle this in Q3 (September) with the progress made on the JS clarinet-sdk 🙌
Hey @sabbyanandan I wanted to point out that the clarinet-sdk is mainly used to be used within Node.js, but not in the browser. So as it is, it could be...
Also, I'm still interesting in adding it in the JS SDK, but just wanted to warn that it won't be available in the browser (at least not out of the...