Throw warnings for exceeding known platform limitations

Not sure if this belongs here or in alexa-app-server.

I spent the last three and a half weeks discovering/troubleshooting the 24k response size limit. Could warnings be thrown in the console so developers would have some clue that the same code will fail on an Alexa device?

https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/alexa-skills-kit-interface-reference

Response Format

This section documents the format of the response that your service returns. The service for an Alexa skill must send its response in JSON format.

Note the following size limitations for the response:

• The outputSpeech response cannot exceed 8000 characters.
• All of the text included in a card cannot exceed 8000 characters. This includes the title, content, text, and image URLs.
• An image URL (smallImageUrl or largeImageUrl) cannot exceed 2000 characters.
• The token included in an audioItem.stream for the AudioPlayer.Play directive cannot exceed 1024 characters.
• The url included in an audioItem.stream for the AudioPlayer.Play directive cannot exceed 8000 characters.
• The total size of your response cannot exceed 24 kilobytes.

If your response exceeds these limits, the Alexa service returns an error.

[nickcoury]

I’ll add another related case. Only certain characters are allowed to be spoken within SSML responses, and if invalid characters are passed it errors the response. I’ve run into a number of times when pulling data from other APIs that include user input.

As a (very) rough illustration, I’ve been using the following RegEx/JavaScript blacklist to filter out some bad characters. It might be worth it to automatically clean the SSML code to make sure it will be valid, perhaps with a good whitelist.

It would likely be optional or a secondary function such as .validatedSay(), given there are a variety of ways to either substitute or remove the text. Would maybe be best as an add-on library even.

Example: text = (text || '').replace(/[^\w\s/<>.,-"']/gi, '').replace('&', 'and').replace('=', 'equals').replace('@', 'at');

[jlguinn]

I’ll take a stab. I created the fork and now it looks like I have some tuts to catch up on writing tests, but this seems like a good spot for me to get started. Thanks for the link.