Maybe a different way of phrasing this is that YOLO mode would be less YOLO, as in less risky, if I could specify a test script (terminal command) that needed to pass (or at least needed to be read by composer)…and the composer were instructed to do this after checking for linter errors but before ending the session.
(and i would feel less like a monkey that copies and pastes terminal errors into the composer pane)
EDIT: I think I answered my own question. This is pretty awesome, but I would appreciate if folks would share their own YOLO mode tips
