Better handling of errors in settings files

Open obycode opened this issue 3 years ago • 1 comments

If a user has a bad mnemonic in a settings file (e.g. settings/Testnet.toml), clarinet will panic instead of reporting a nice error message. Users will often see this if they have forgotten to replace the default "<YOUR PRIVATE TESTNET MNEMONIC HERE>".

$ clarinet publish --testnet

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: BadWordCount(5)', src/types/chain_config.rs:214:42
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Mar 08 '22 13:03 obycode

I agree. Please make this happen.

Mar 08 '22 13:03 unclemantis

Addressed with latest

Oct 06 '22 14:10 lgalabru