The bug came from a change in the message being sent to the front end. Node bindings in the answers used to be arrays for set nodes and strings for not, but now they're all arrays. This fix gets the question graph node and checks the 'set' boolean flag. If the node isn't a set, we either take the node binding string (for backwards compatibility) or the first element of the array of bindings (even if there are more, the node isn't a set).
The bug came from a change in the message being sent to the front end. Node bindings in the answers used to be arrays for set nodes and strings for not, but now they're all arrays. This fix gets the question graph node and checks the 'set' boolean flag. If the node isn't a set, we either take the node binding string (for backwards compatibility) or the first element of the array of bindings (even if there are more, the node isn't a set).