feat(cli): CAN-340 Show step name on error

[noahlitvin]

Needs more testing/verification

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6a833ee

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 6a833ee. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 1 target

• lerna run build --ignore cannon-website --ignore @usecannon/indexer --ignore repo --ignore @usecannon/api

---

Sent with 💌 from NxCloud.

[mjlescano]

Mmm, tried it out for example putting an erroneous contract name but in both cases, on main and this branch I get the step name:

Maybe there's another use case that I'm not trying?

[noahlitvin]

Yea, I think the improvement is surfaced if e.g. it throws an error parsing a template string? (Like see what follows the log output when it's in the new position from this pr)

[mjlescano]

This PR showed no difference on these three cases (first two we can still see the name on main):

1. When doing something invalid on templating:

2. When throwing an error on constructor:

3. When adding an invalid depends, this case didn't show the step name on any branch:

Case 3. is the one we should be fixing probably, maybe am i missing some other case?

[dbeal-eth]

the problem with this implementation is that it prints out the step name every single time, even if its not actually being executed

in order to determine whether a step should be executed or not, its configuration needs to be computed, which requires doing some things which may result in error.

I think the only approach we have to this is adding a fake log message for this if an error is generated and only in that case.