feat: add generic msg on failed transactions

[Jonatan-Chaverri]

Task name here

Fixes #573

Types of change

• Feature
• Bug
• Enhancement

Comments (optional)

[metalboyrick]

GM @Jonatan-Chaverri , thanks for your PR! You got the idea right. Leaving some comments and thoughts for improvement

1. Can we improve the style? (fix the padding and margins)

2. Can we have a clickable link that points us to the specific log from the toast? so that it is easier to trace the error logs for other developers

3. Can we extract some common errors like insufficient balance or approval required? We can discuss this further if you think this is possible / not possible

[metalboyrick]

GM @Jonatan-Chaverri, any updates on this?

[Jonatan-Chaverri]

@metalboyrick I will work on this today and provide an update at the EOD

[Jonatan-Chaverri]

@metalboyrick I have addressed the first two requests.

For the third, we can have a file similar to this
https://github.com/starknet-io/types-js/blob/main/src/api/errors.ts#L107

and translate each code to a more verbose error message, is that what you mean? if not, please elaborate a little more. Thanks.

[metalboyrick]

@Jonatan-Chaverri Yeah something like that would be great, because it gives better clarity to users rather than some strange JSON. You can try out some common ones like insufficient balance, no approval. (be mindful of which errors are common which errors can be user-specific)

[Jonatan-Chaverri]

@metalboyrick I updated the PR, let me know your thoughts, thanks.

[metalboyrick]

Thanks for the fix!

Can fix the styling ser, please make sure the margins and paddings are not too wide, we do not need the dark background as well.

Also, I did not see the common error po up when transferring insufficient balance

[Jonatan-Chaverri]

@metalboyrick ok, made some changes to fix the margins, this is how it looks now

Also, I tried getting insufficient balance error to test too and this is the error content my function is getting

TypeError: Failed to fetch does not match any known common error so that's why it is not showing in the toast.

I'm not aware of how all starknet common errors are printed, so the file I created is based on assumptions that at least keywords will appear in the error, but again is not 100% reliable until we can confirm that (or if you know how to confirm error messages, you can point me to it and I will update)