DCR: Add Slot property to Prompt class

[tomlm]

Issue

Currently prompt classes require the caller to take the output of a prompt and assign it to a slot. This causes the following:

• on a waterfall, the next step needs to collect the slot value and save it
• it pushes a code requirement into the consumption of the Prompt.

Proposed change

If we change the prompt class to have a property called "Slot" it can be configured to automatically "fill the slot" without requiring code behind.

Component Impact

Base prompt class in each SDK

Customer Impact

Should be additive, if the property is set people can start using it.

Tracking Status

Dotnet SDK

• PR
• Merged

Javascript SDK

• PR
• Merged

Samples

• PR
• Merged

Docs

• PR
• Merged

Java SDK - n/a Dialogs library doesn't exist on java yet.
Python SDK - n/a Dialogs library doesn't exist on python yet.

[dcr]

[Stevenic]

The issue is, the Prompt doesn't have access to the memory where the value needs to be stored. Each dialog has its own isolated storage which it uses to accumulate values returned by calling prompts or other dialogs. I haven't figured out a good workaround for this as everything I've thought of either violates the underlying stack model or comes with its own side effects.

[tomlm]

I think we would have to create something like this:

class DialogSlotResult : DialogResult
{ 
     public string Slot 
    public object Result
}

[gabog]

I think this issue is pretty old now and does not apply to the current state of the SDK, closing.