-
-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
toIntent() improvement #55
Comments
Hi @terloon, thanks! Is writing I would do it like this:
Am I missing something? |
So my use case was:
But you're right, it doesn't really save much since this is done once and in NEW_SESSION would probably where this would likely be used. Also, new to node.js (or at least its been a while since I did javascript), but I thought doing this:
would just make the first argument (or arguments[1]) be an object like:
Closing this issue. Thanks for the feedback. |
Hi @terloon, ah I get it, you want to use it inside So, you have tried just using
Because actually this should work (cc @aswetlow). We'll look into it |
I think I narrowed down the case where I had to do this. On the Alexa Test Simulator, if I don't pass in the input, when I perform an invocation of the voice app with a command, the input is lost. So if my invocation is "hello world" with a skill like "start thing with number 1", if I say: "ask hello world start thing with number 1", it would lose the slot input parameter. |
Hey yes, this is due to the 'NEW_SESSION' handler. |
Gotcha. Right now I am getting around it by doing what I initially mentioned:
|
This got resolved some time ago |
On my initial use of toIntent(), I made a horrible assumption that it would also automatically route the inputs. So what I had to do was:
Could we add something like:
The text was updated successfully, but these errors were encountered: