Should slots generally be reset to None after action is executed?

[smn-snkl (Simon)]

@akelad @Ghostvv: Running into a similar issue like this one regarding “forcing” slots to be asked at least once during a FormAction.

I realized that resetting slots doesn’t solve issue #1 from my initial post:

@smn-snkl

1. If I don’t reset it, how can I avoid booking the same table again, just because the slots were still filled from the previous attempt?

Because, e.g. situations like these might appear, which still suffer from the same problem:

* user_likes{"item": "strawberries"}  # "I like strawberries"
  - utter_user_likes
* order_food
  - form_food
  - form{"name": "food"}
  - form{"name": null}

Is there a “thought-through” solution for how to avoid that forms automatically “pre-filled” slots? It’s very inconvenient in situations like the one above to ask the user for confirmations (like “Do you want to order strawberries?” in the story from above). Ideally, I want to achieve something like this:

Requirement

Every slot that is at some point during the FormAction part of the required_slots, must be asked or confirmed at least once during a FormAction.