Debugging gets extremely hard, especially when using nested features of the library. Traceback ends up being nothing but question marks all linking the the base runner functions.
This will be included in a future release.
Setting debug=true in multi settings on init, will include extra info on all objects which multi.error will capture and display when an error happens. Just need to ensure performance isn't impacted.
Debugging gets extremely hard, especially when using nested features of the library. Traceback ends up being nothing but question marks all linking the the base runner functions.
This will be included in a future release.
Setting
debug=truein multi settings on init, will include extra info on all objects which multi.error will capture and display when an error happens. Just need to ensure performance isn't impacted.