Thanks. Although I didn’t mean yes/no in that more limited sense of button pushing, but assumed (sorry) it was obvious that we’re talking to the user conversationally. So I probably should have said affirm or deny instead of yes or no.
And thanks also for the FormValidation suggestion, although that seems like an overly complicated approach.
Validation functions (which use
super()) should be used for performing validation on the data itself, that’s what validation is. (It can also be validated against a back end API.)
Verification (asking the user to confirm something is correct) is a logically different operation, and only bears similarity in a colloquial sense of the words. Adding a verification step inside form validation, where you dispatch a message to the user, collect their response, and then pass flow control state seems fraught.
A good way to think about this is that validation should fail if an error is thrown. You’re making sure everything is ‘kosher.’ Verification isn’t throwing any errors (user response is not an error.)
We’re looking for a way in Rasa to verify with the user that the information is correct, which seems (a) impossible to do for the last/only question on a form, and (b) impossible to do conversationally, rather you need to strictly enforce a category choice of “yes” or “no.”
If either (a) or (b) are not true, please do LMK!
And thanks again for the suggestions!