Skip to content
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

Throws an error as elicitSlot when the invoking intent is not associated #98

Open
jperata opened this issue Dec 6, 2018 · 0 comments
Open
Labels

Comments

@jperata
Copy link
Contributor

jperata commented Dec 6, 2018

Is your feature request related to a problem? Please describe.
Issue an elicitSlot response in a lambda with a slot name which isn't associated with the Intent which triggered the lambda then virtual Alexa accepts this and returns the Dialog elicitSlot response. However, this is an illegal operation as "real Alexa" throws an error as elicitSlot can only be issued with a slot name associated with the invoking intent.

Describe the solution you'd like
Throw an error similar to what Alexa does.

Describe alternatives you've considered
Keep logic as it is, it's a minor difference

Additional context
We should update the documentation

@jperata jperata changed the title throws an error as elicitSlot can only be issued with a slot name associated with the invoking intent Throws an error as elicitSlot when the invoking intent is not associated Dec 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants