Skip to content

Commit

Permalink
chore: create a const to hold the panic message (#2122)
Browse files Browse the repository at this point in the history
chore: create a const to hold the panic message
  • Loading branch information
TomAFrench authored Aug 2, 2023
1 parent b0fbc53 commit 292724f
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions crates/nargo_cli/src/main.rs
Original file line number Diff line number Diff line change
Expand Up @@ -3,12 +3,12 @@
use color_eyre::{config::HookBuilder, eyre};
use nargo_cli::cli::start_cli;

const PANIC_MESSAGE: &str = "This is a bug. We may have already fixed this in newer versions of Nargo so try searching for similar issues at https://github.com/noir-lang/noir/issues/.\nIf there isn't an open issue for this bug, consider opening one at https://github.com/noir-lang/noir/issues/new?labels=bug&template=bug_report.yml";

fn main() -> eyre::Result<()> {
// Register a panic hook to display more readable panic messages to end-users
let (panic_hook, _) = HookBuilder::default()
.display_env_section(false)
.panic_section("This is a bug. We may have already fixed this in newer versions of Nargo so try searching for similar issues at https://github.com/noir-lang/noir/issues/.\nIf there isn't an open issue for this bug, consider opening one at https://github.com/noir-lang/noir/issues/new?labels=bug&template=bug_report.yml")
.into_hooks();
let (panic_hook, _) =
HookBuilder::default().display_env_section(false).panic_section(PANIC_MESSAGE).into_hooks();
panic_hook.install();

start_cli()
Expand Down

0 comments on commit 292724f

Please sign in to comment.