/watchout/go/<cue> issues run command even when cue is not present

[ptcr-marino]

Prerequisites

• Using npm
• Using an up-to-date main branch
• Using latest version of devtools. Check the docs for how to update
• Tried solutions mentioned in #400
• For issue in production release, add devtools output of DEBUG_PROD=true npm run build && npm start

Expected Behavior

When issuing the command /watchout/go/{cue} over OSC, the application should not issue a run command if watchout returns an error that the cue named {cue} is not found. The expected behavior is present in osc-watchout which makes this a regression.

Current Behavior

The application blindly issues a run command in the same line as the gotoControlCue command, causing the timeline to start running even if the cue is not found.

Steps to Reproduce

1. Send a /watchout/go/{cue} command where {cue} is a string that is not present in the watchout timeline as a control cue

Possible Solution (Not obligatory)

Check the response to gotoControlCue and branch if the response contains the string "error" - See the osc-watchout code for an example of the correct behavior.

[jshea2]

Thanks for catching this. Here's v1.3.0 with the bug fix:
https://github.com/jshea2/OSC-for-WATCHOUT/releases/tag/v.1.3.0