Rename FORM_PREFIX to ACTIVE_LOOP_PREFIX

[wochinge]

Follow up issue from #6409:

The FORM_PREFIX (see here should be renamed to ACTIVE_LOOP_PREFIX with a value active_loop: .

Todos

• rename
• make sure the old prefix is deprecated
• adapt the docs
• make sure interactive learning still works as expected
• Collect Rasa X implementations in an issue (e.g. extend this one). The FORM_PREFIX is used in the story view / end-to-end story view

[wochinge]

cc @akelad

[chkoss]

Do we actually want to do this? This prefix is only used in the markdown readers, and markdown training data will be deprecated anyways.

[wochinge]

Do we actually want to do this? This prefix is only used in the markdown readers, and markdown training data will be deprecated anyways.

You're completely right 🙈

@degiz We need something similar for the yaml e2e_tests training data.

We use the FORM_PREFIX do mark in end-to-end tests which utterances are part of happy form paths and which belong to unhappy paths. unhappy paths are when the form / loop rejected its execution (e,g. because no slot was filled) and other policies get to predict the next action (e.g. handling chitchat then).

An alternative to the FORM_PREFIX would be that users explicitly define an ActionExecutionRejected in their stories whenever they enter an unhappy path. The problem is that they'd need to know internals of the FormAction to understand when they need to do that.

[degiz]

@tmbo since you've just worked on that, do we have yaml e2e stories that test the forms?

[tmbo]

we don't have them yet, but I think adding an attribute that can be used instead of the form prefix is the way to go for now

[wochinge]

Do we want this for the alpha 3 @tmbo @degiz ?

[tmbo]

the implications of this issue are that you cant use story tests when you are using any loops right?

[Ghostvv]

form_prefix is deprecated even in markdown, do we need to rename it?

[Ghostvv]

the new RulePolicy doesn't use it

[wochinge]

Ah, we don't need it because of the new tracker featurization, correct?

[Ghostvv]

rather, the new applied_events with removing happy loop actions

[wochinge]

Yes, that's what I mean. Then we can leave this as it is for old markdown.