-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve no deployment error message in status #527
Comments
kanej
added
status:ready
This issue is ready to be worked on
and removed
status:triaging
labels
Oct 9, 2023
Let's rethrow with a message that includes the ignition error code. The errors thrown should be |
kanej
added a commit
that referenced
this issue
Oct 10, 2023
We are removing support for invoking a module just by giving its file name. Instead the tasks will work in terms of a full or relative path to the module file. Users prefer this for autocomplete reasons anyway, but it removes confusion as to whether it is the `ModuleId` or filename that is in use here. Resolves #527.
kanej
added a commit
that referenced
this issue
Oct 10, 2023
We are removing support for invoking a module just by giving its file name. Instead the tasks will work in terms of a full or relative path to the module file. Users prefer this for autocomplete reasons anyway, but it removes confusion as to whether it is the `ModuleId` or filename that is in use here. Resolves #527.
kanej
added a commit
that referenced
this issue
Oct 10, 2023
We are removing support for invoking a module just by giving its file name. Instead the tasks will work in terms of a full or relative path to the module file. Users prefer this for autocomplete reasons anyway, but it removes confusion as to whether it is the `ModuleId` or filename that is in use here. Resolves #527.
kanej
added a commit
that referenced
this issue
Oct 10, 2023
We are removing support for invoking a module just by giving its file name. Instead the tasks will work in terms of a full or relative path to the module file. Users prefer this for autocomplete reasons anyway, but it removes confusion as to whether it is the `ModuleId` or filename that is in use here. Resolves #527.
kanej
pushed a commit
that referenced
this issue
Oct 11, 2023
Use a whitelist to determine whether a code `IgnitionError` should be rethrown as a Hardhat plugin error. This list can be added to as more Ignition errors are identified as being better displayed as HH errors. We intend to extend the HH error code mechanism to give Ignition even more control over the display of errors in HH. This change only adds this rethrow for status and the unrecognised deployment entry currently. Fixes #527.
kanej
added a commit
that referenced
this issue
Oct 12, 2023
We are removing support for invoking a module just by giving its file name. Instead the tasks will work in terms of a full or relative path to the module file. Users prefer this for autocomplete reasons anyway, but it removes confusion as to whether it is the `ModuleId` or filename that is in use here. Resolves #527.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you run the status command with a non-existant deployment id you get:
At the least the stack trace should be removed. Maybe a pattern to follow is HHs:
The text was updated successfully, but these errors were encountered: