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
When debugging browser related issues such as encoding/decoding bugs in the browser for example, it could be useful to have a DevTools plugin that would display the relevant info.
Let's say we are having an issue planting a seed, it would be helpful to see what the result of a contract call would be in the browser.
| Wallet Connected | Program Type Called | Result of Program Execution | Gas Expended for Last Transaction | Last Transaction Hash ||------------------|---------------------|-----------------------------|------------------------------------|----------------------|||||||||||||
Of course these specific fields may relevant to that use case and so there would need to be some discussion about what's generic enough to apply to more use cases. Open to feedback.
This would significantly improve the debugging experience along with #2298
The text was updated successfully, but these errors were encountered:
Motivation
When debugging browser related issues such as encoding/decoding bugs in the browser for example, it could be useful to have a DevTools plugin that would display the relevant info.
Usage example
An example would be debugging the sway-farm dApp.
Let's say we are having an issue planting a seed, it would be helpful to see what the result of a contract call would be in the browser.
Of course these specific fields may relevant to that use case and so there would need to be some discussion about what's generic enough to apply to more use cases. Open to feedback.
This would significantly improve the debugging experience along with #2298
The text was updated successfully, but these errors were encountered: