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
{{ message }}
This repository has been archived by the owner on Jun 23, 2020. It is now read-only.
Add a button that quickly fires up our block explorer / debugger. Best case is in-line with the Run and Test buttons and having it open in a new tab. Else it's not clear for the newbie how to debug things.
Honestly unsure what the best syntax is -- it's technically the "Explorer" (with explorer icon) but "debugger" (with a bug icon) is more inline with why someone from the IDE . would want to click it in that context.
The text was updated successfully, but these errors were encountered:
I think the best would be to make specific transactions linked from JS console (i.e. Nearlib error / success messages should include link to debugger).
Also after thinking about it for a while – we also can make a real debugger. Every transaction in explorer, etc can have a "Debug" link which will try to run contract code in browser (with same inputs).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add a button that quickly fires up our block explorer / debugger. Best case is in-line with the Run and Test buttons and having it open in a new tab. Else it's not clear for the newbie how to debug things.
Honestly unsure what the best syntax is -- it's technically the "Explorer" (with explorer icon) but "debugger" (with a bug icon) is more inline with why someone from the IDE . would want to click it in that context.
The text was updated successfully, but these errors were encountered: