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

Can Fulfill Intent handling of no value #5

Open
terrenjpeterson opened this issue Jul 21, 2018 · 1 comment
Open

Can Fulfill Intent handling of no value #5

terrenjpeterson opened this issue Jul 21, 2018 · 1 comment
Labels

Comments

@terrenjpeterson
Copy link
Owner

If a no storm name is provided, an error gets thrown. Need more robust handling of this query to check that a name has been provided.

"request": {
"type": "CanFulfillIntentRequest",
"requestId": "b7cce0ed-cb3b-4cbb-97c6-bc8a22e98c19",
"timestamp": "2018-07-21T11:08:20Z",
"locale": "und",
"intent": {
"name": "GetStormDetail",
"slots": {
"Storm": {
"name": "Storm"
}
}
},
"dialogState": "STARTED"
}

@terrenjpeterson
Copy link
Owner Author

terrenjpeterson commented Jul 21, 2018

The way that the function is written it currently expects a "value" attribute - see example below.

"request": {
"type": "CanFulfillIntentRequest",
"requestId": "b7cce0ed-cb3b-4cbb-97c6-bc8a22e98c19",
"timestamp": "2018-07-21T11:08:20Z",
"locale": "und",
"intent": {
"name": "GetStormDetail",
"slots": {
"Storm": {
"name": "Storm",
"value": "Katrina"
}
}
},
"dialogState": "STARTED"
}

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

1 participant