We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Forge
Currently should panic with single felt error messages
#[should_panic(expected: 'Some Error Message')]
If possible what would be nice is where SomeContract::Error::SOME_ERROR_MESSAGE is a const felt252
SomeContract::Error::SOME_ERROR_MESSAGE
felt252
#[should_panic(expected: SomeContract::Error::SOME_ERROR_MESSAGE)]
Every time when I update the error message in a contract I need to update all the should_panic s as well. This will elimate that concern
should_panic
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Which component is your feature related to?
Forge
Feature Request
Currently should panic with single felt error messages
#[should_panic(expected: 'Some Error Message')]
If possible what would be nice is where
SomeContract::Error::SOME_ERROR_MESSAGE
is a constfelt252
#[should_panic(expected: SomeContract::Error::SOME_ERROR_MESSAGE)]
Every time when I update the error message in a contract I need to update all the
should_panic
s as well. This will elimate that concernThe text was updated successfully, but these errors were encountered: