-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Rename Form
to Loop
event
#6409
Comments
@mjaycub Do you know if there is any special handlings for Rasa Open Source |
Found these lines in the frontend, but that seems easy to handle: |
@wochinge I can have a look tomorrow if you'd like, today is blocked up by IVC work |
That would be great. It's not critical but needs to be done for 2.0 compatibility. |
@wochinge it doesn't look like we do anything special with Will I open a PR with these changes? |
I don't know. Will you? 😄 I'd hold off a bit - could be that also rename |
Haha, was just curious if you wanted to touch the frontend or if you wanted me to do it! 😄I can do it, just follow up when you thing it's time to do so 👍 |
As part of the
|
re-opening this. Doesn't make sense to close it at this stage 👍 |
Feel free to wrap this up. Otherwise I can do it when I'm back. |
As part of the
RulePolicy
refactoring, we introduced the concept of aLoop
which represents conversation parts which areif
andelse
sIn contrast
Form
s to request information from the user and fill required slots.This means every
Form
is aLoop
, but not everyLoop
is aForm
. E.g. theTwoStageFallback
was implemented using theLoop
concept but it's not a Form.Form
event toLoop
eventForm
events can still be retrieved from the tracker storesadapt Rasa X backendnot required (the tests which involve this are commented out anyway)active_form
active_loop
eventsThe text was updated successfully, but these errors were encountered: