Dr. Simon Harrer

Thanks for your points. I suggest to focus first on the API, and then think on how we can implement this. Current commands: start, next, done, timer, and reset. I...

Thanks for the quick response. All those messages basically verify that the result was successful. The mob tool basically knows two result *status*: *success* and *error*. In case of an...

Not really regarding the errors. Because after an error, the tool terminates. It would only help with warnings, but we don't really have a lot of them. But checking the...

That is my question with regard to errorDetail that would contain only the error messages and output would contain everything.

Awesome comments. Thank you all for them! Current draft. Feel free to comment further! *next* and *fix* are optional. ```json { "status": "success", "next": { "instruction": "To finish, use", "command":...

Beep is based on https://github.com/hajimehoshi/oto which requires some other software that may need to be installed by the user manually.

Have a look at https://github.com/remotemobprogramming/mob/pull/235 for my try at it

Behavior is not fully downwards compatible (see the replacing of `%s` with the voice message), it will break either way except when introducing yet another configuration option. So instead of...

sounds reasonable.

> I'd like to run (some) tests after successfull mob start, so that I can validate the current state of the code. > > To enter solution-land I'd suggest adding...