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
Currently FAULT messages don't get output to the VSCode PROBLEMS, TERMINAL or other output areas. You have to go to the transaction detail screen in the DevTracker to see the fault message, which means you have to know which block to go to and also know in the first place that a FAULT occurred. Easy when you're still in the early stages of dev but progressively harder workflow later (my two cents). I would like to see those messages in the TERMINAL area and even better, have that window pop to the foreground automatically if a FAULT message was logged if that is possible.
The text was updated successfully, but these errors were encountered:
devhawk
transferred this issue from N3developertoolkit/neo-blockchaintoolkit-library
Jun 25, 2021
If we do this, I think we'd first need a change to Neo Express to output FAULTs to the console (using some format that the DevTracker expects and parses). This behavior could probably be hidden behind a flag.
As of June 2021, the ExpressLogPlugin writes transaction execution failures to stderr. DevTracker shows the full Express output in a terminal window. TX Faults are shown in red in order to distinguish them from other messages. @roschler is this sufficient?
Currently FAULT messages don't get output to the VSCode PROBLEMS, TERMINAL or other output areas. You have to go to the transaction detail screen in the DevTracker to see the fault message, which means you have to know which block to go to and also know in the first place that a FAULT occurred. Easy when you're still in the early stages of dev but progressively harder workflow later (my two cents). I would like to see those messages in the TERMINAL area and even better, have that window pop to the foreground automatically if a FAULT message was logged if that is possible.
The text was updated successfully, but these errors were encountered: