Brice
When running clarinet on Windows in a bash terminal (Git Bash), I am seeing the escape codes instead of the colors: ``` $ clarinet check ←[1;31merror←[0m: use of unresolved function...
We currently handle checking for un-closed brackets in the input via the `complete_input` function. This should instead be handled in a `Validator` passed into the `Editor`. I checked if the...
Related to hirosystems/clarity-repl#115, there should also be a command to read a file and execute all expressions in that file within the current REPL context.
From [Discord](https://discord.com/channels/621759717756370964/839633619261456444/981917208504573972): The REPL will crash when using `try!` or `unwrap-panic!` on a contract call returning an error. For example, using this contract: ```clarity (define-public (bad (arg uint)) (if (is-eq...
With the way that the debugger is implemented, it should not be too difficult to enable a debug session on a live devnet. There are just packets being sent back...
For example, with the debugger-demo repo, if you try to debug the expression `(contract-call? .foo hello .bat)`, you should see an error somewhere saying "error: use of unresolved contract 'ST1PQHQKV0RJXZFY1DGX8MNSNYVE3VGZJSRTPGZGM.bat'"...
Now that clarity-reply is merged into clarinet, we need to merge in its workflows, for testing and releasing.
This change checks for reserved names in addition to checking for names previously defined by the user. Fixes: #418
The todo here should be addressed soon, since this can often result in difficult to understand failures in unit tests. https://github.com/hirosystems/clarinet/blob/7658e067202b5f641e92d1bf924ffc2ab0348b72/src/runner/api_v1.rs#L378-L386