-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
validate user input in activation #6172
Conversation
@@ -43,6 +44,7 @@ async def is_activated( | |||
|
|||
# default implementation checks if form active | |||
def _default_activation_events(self) -> List[Event]: | |||
# TODO if this is in the loop action, probably it should not be `Form` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean we should rename the event?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, and also think whether we want to use the same event name for forms and loops. So we need to think through how they interact with each other. Let's tackle it separately. I added TODO
so that we don't forget
Co-authored-by: Tobias Wochinger <t.wochinger@rasa.com>
* have one validate function for the whole form * remove unused function * more tests * remove unnecessary ignores * add clarification comment * validate user input in activation (#6172) * validate user input in activation Co-authored-by: Tobias Wochinger <t.wochinger@rasa.com> * more tests for entity extraction * more `FormAction` tests * add todo Co-authored-by: Vladimir Vlasov <vladimir@rasa.com>
Proposed changes:
Status (please check what you already did):
black
(please check Readme for instructions)