Due to the fact that APLA reprompt was introduced there is no need to include outputSpeech - especially when it's empty or null.
Motivation and Context
Currently When calling withReprompt with empty or null text, outputSpeech gets populated with empty <speak></speak>. It causes validation errors (like The skill should not respond to intent requests with empty text or SSML in reprompt while keeping the skill session open.) and it's redundant when using APLA reprompt as directive parameter.
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist
[x] My code follows the code style of this project
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[x] I have read the README document
[x] I have added tests to cover my changes
[x] All new and existing tests passed
License
[x] By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Description
Due to the fact that APLA reprompt was introduced there is no need to include
outputSpeech- especially when it's empty or null.Motivation and Context
Currently When calling
withRepromptwith empty or nulltext,outputSpeechgets populated with empty<speak></speak>. It causes validation errors (likeThe skill should not respond to intent requests with empty text or SSML in reprompt while keeping the skill session open.) and it's redundant when using APLA reprompt asdirectiveparameter.Types of changes
Checklist
License