-
Notifications
You must be signed in to change notification settings - Fork 46
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
Feat: Descriptive Error Message #23
Conversation
636029d
to
ce0ccc4
Compare
Do you have a permit link I can test this with? |
here's one |
Available commands
|
balance and approval @pavlovcik |
Available commands
|
I need to think about the design to convey this information clearly and concisely. I feel like this should be in the "more details" I do like your implementation here, but the original bounty was supposed to be simpler: writing in plain english the issue when the errors dump into the DOM. |
okay, I'll do and updating u here @pavlovcik |
should I delete the treasury field above? @pavlovcik |
Available commands
|
Well to clarify, we should still have the plain english error when the claim fails (like when the raw MetaMask JSON RPC error dumps in the red monospace text on the DOM.) Please show both e.g:
However what you already implemented here could be technically considered as a separate bounty. Yes you should remove the treasury field. |
upped |
9ab35ec
to
80107d2
Compare
Git won't let me test this lol maybe you can rebase to main head |
rebased @pavlovcik |
Not sure why I'm getting the same error. |
might be your git client having issues |
Looks good. Strangely enough it crashes on Safari right at the function execution but technically that's not in scope of the bounty. But still concerning that there's inconsistencies with Safari and Chrome for a simple promise.
|
use `eslint-plugin-filename-rules`
Resolves #21