createStateHandler(s) about alexa-skills-kit-sdk-for-nodejs HOT 2 CLOSED

Hi Craig,

We chose 'handler' vs 'handlers' since the function returns a single object that maps to a single state, even though it can contain multiple listeners. You then register event listener functions inside of that object. Providing an object as a parameter to CreateStateHandler is a convenience.

For example, the following is valid:

var inProgressHandler = Alexa.CreateStateHandler('InProgress');

inProgressHandler['LaunchRequest'] = function(){ ... }

Does that make sense?

As to your other question, in the example, newSessionHandlers would be equivalent to

var newSessionHandlers = Alexa.CreateStateHandler(); // The 'null' state

inProgressHandler['NewSession'] = function(){ ... }

You would still need to have something like the above to catch the first-ever invocation of the skill, before any attributes (including the state string) have been set.

Of course, you don't have to use the state feature at all, especially if it is a simpler skill. It just helps to manage complexity as the number of intents go up.

from alexa-skills-kit-sdk-for-nodejs.

Thanks @deegles,

I guess when I first came to it I didn't see them as "listeners" but rather "handlers", ta.

Still not sure on the "new session being a special case" thing, perhaps if state was the second argument it would have worked out. I actually like the declarative state handley stuff and would have liked to see it used for all states but ok, ta.

from alexa-skills-kit-sdk-for-nodejs.