Fix event type #12
Open
Fix event type #12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
August 29, 2020 17:50
… that are different from intents.
…uest type id IntentRequest
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Alexa payloads are different based on the request type: if the type is "IntentRequest" there is also the "name" of the intent, who is configured in the Alexa developer portal by the developer; but if the type is "LaunchRequest" or "SessionEndedRequest" there is no "name" field, resulting in an error. These special types are used from Alexa to send the first opening of the skill (when you open a skill without declaring an intent) or when it needs to be closed gracefully.
With this PR my aim is to add the management of these requests so that it doesn't break anything. Tested with unit tests and with a production application.