Hugo C
Hugo C
> do you know what it would take to get it ready to run in the browser? Probably not much, a bit of refactoring and some webpack config, it's probably...
@leahjlou > it will depend on the UX we want Could we world on the UX first and then on the implementation? Usually, I'm willing to build features on clarinet...
> not need completely finalized designs, but I believe that we do need a general idea of what we envision for the UX 💯 And the line number thing is...
Thanks for reporting @friedger The clarity-version set in deployments is for internal use in clarinet but doesn't impact the contract on chain. Because you can't set the clarity version of...
> The clarity version can be specified when deploying a contract. Ah my bad, I wasn't aware of that. 1. On the clarinet side, we should double check that the...
Ok I see. We'll need to address that, thanks!
@planbetterHQ @friedger I'm assuming both of your use case are about PoX contracts right?
Could it be feasible / desirable to only triggers the actions impacted by a change. For example, an update to the clarity-vscode component code has no impact on clarinet or...
Any thoughts regarding the tags and versions difference between Clarinet and the VSCode extension?
Deno (and especially our outdated version) brings many compilation issues. To be re-assessed once we remove Deno as part of https://github.com/hirosystems/clarinet/issues/1065