-
Notifications
You must be signed in to change notification settings - Fork 34
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
Missing support for new built-in intent AMAZON.SelectIntent #115
Comments
Hi Octavio, we are looking to add support for this in our upcoming development. In the meantime, you can work around this by using our request object. It works like this:
Additional info on the skill request object is here: Using the set method you can essentially manipulate the JSON as needed. Not an ideal solution, but should get you past this error message. We are keeping this issue open for scheduling in an upcoming sprint. |
Thanks @jkelvie I was able to use it that way exactly. Sorry for not posting it before! |
Hi Tyler, we do not have a current timeline for this - I would recommend the workaround as mentioned above, imperfect though it may be. |
@jkelvie thanks for the reply! I really appreciate it. |
Description:
The framework throws an error when trying to use the
AMAZON.SelectIntent
built-in intentEnvironment:
Steps To Reproduce
Steps to reproduce the behavior:
reply = await platform.intend('AMAZON.SelectIntent', { ListPosition: '3' });
Expected behavior
virtual-alexa should return an intent request for
AMAZON.SelectIntent
with the slot value I defined in the slots. It could be one of the 4 intents allowedActual behavior
It returns the following error:
Error: Trying to add slot to intent that does not have any slots defined
Code example
The text was updated successfully, but these errors were encountered: