Currently each dialog on bot is a function array that need to be preregistered at server start up.
It leads to 2 problems.
callStack = [ fn1, fn2, fn3]
bot.dialog(id, callStack)
Is there a way not to define the callStack upfront that is common for all users of that dialog. The dialog should be able to jump to functions that are data driven than code driven. ie. generic functions.
e.g. two dialogues one wants to get date and another wants to get text. They can use the same function but invoke the necessary code to prompt a date or text based on passed params to that function.
The function should have a way to get additional params passed to it.
This change in design pattern is needed to prevent code bloat and provide some dynamic behavior.
@ubreddy You are in luck. The Bot Framework team is actually in the process of a complete re-write of the BotBuilder SDK dialog system in the v4 line.
Stay tuned for updates and SDK v4 preview early next year.
Great! looking forward to it. Hope we can get early in Jan ? or am I being ambitious :)
that's the plan
@nwhitmont Any date finalized for this SDK release ? or can we have a preview of the new design before the release?
Most helpful comment
@ubreddy You are in luck. The Bot Framework team is actually in the process of a complete re-write of the BotBuilder SDK dialog system in the v4 line.
Stay tuned for updates and SDK v4 preview early next year.