You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, testing contract interoperability can fail with the ENTRYPOINT_FAILED error when anything fails in the entrypoint.
It makes it really hard to find the actual cause of the error. Describe Preferred Solution
It would be great if the error message returned was actually the one specified in the contract. For example, if my contract panics with a panic_with_felt252('not implemented') error, it should return not implemented.
Describe Alternatives
Related Code
Additional Context
If the feature request is approved, would you be willing to submit a PR? (Help can be provided if you need assistance submitting a PR)
Yes
No
The text was updated successfully, but these errors were encountered:
Feature Request
Describe the Feature Request
Currently, testing contract interoperability can fail with the
ENTRYPOINT_FAILED
error when anything fails in the entrypoint.It makes it really hard to find the actual cause of the error.
Describe Preferred Solution
It would be great if the error message returned was actually the one specified in the contract. For example, if my contract panics with a
panic_with_felt252('not implemented')
error, it should returnnot implemented
.Describe Alternatives
Related Code
Additional Context
If the feature request is approved, would you be willing to submit a PR?
(Help can be provided if you need assistance submitting a PR)
The text was updated successfully, but these errors were encountered: