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
Run yarn && yarn main on https://github.com/bbenligiray/fulfillment-analysis and you will see fail() being called with errorMessages such as call revert exception; VM Exception while processing transaction: reverted with reason string "In... This is because the static test call before the fulfillment errored. There are two problems with this:
It's difficult to make sense of for the user. Only two characters of the revert string is visible.
Use a generic errorMesssage, but bubble up the revert string when possible
I did make use of the first two characters of the revert message while debugging, so I'm not 100% on 1. That being said, the revert string is embedded in the API response and the format of that likely depends on the blockchain provider implementation, so I'm not sure if this can be done in a generalized way. If 2 seems not doable, 1 is still the way to go because in most cases two characters won't be enough so we won't be losing too much.
The text was updated successfully, but these errors were encountered:
Refer to https://api3workspace.slack.com/archives/C02AYRX8D89/p1681907159870799
Run
yarn && yarn main
on https://github.com/bbenligiray/fulfillment-analysis and you will seefail()
being called witherrorMessage
s such ascall revert exception; VM Exception while processing transaction: reverted with reason string "In...
This is because the static test call before the fulfillment errored. There are two problems with this:I think there are two options:
errorMessage
insteaderrorMesssage
, but bubble up the revert string when possibleI did make use of the first two characters of the revert message while debugging, so I'm not 100% on 1. That being said, the revert string is embedded in the API response and the format of that likely depends on the blockchain provider implementation, so I'm not sure if this can be done in a generalized way. If 2 seems not doable, 1 is still the way to go because in most cases two characters won't be enough so we won't be losing too much.
The text was updated successfully, but these errors were encountered: