Ievgenii Krevenets
Ievgenii Krevenets
Similar to what we have for Alexa skill https://github.com/internetarchive/internet-archive-google-action/tree/master/functions/tests/integration/alexa
# Platforms limitations ## Alexa Skill ### Limitations > The `outputSpeech` response cannot exceed 8000 characters. (https://developer.amazon.com/docs/custom-skills/request-and-response-json-reference.html#response-format) https://github.com/actionably/dashbot/commits/master/src/dashbot-google.js [forum question](https://forums.developer.amazon.com/questions/109422/reading-text-greater-then-8000-characters.html?childToView=180923#answer-180923) ## Action of Google ### Limitations > Chat bubbles are...
Dialog as: ```yaml - scenario: 'play music by: randomly play jazz 78s' dialog: - user: 'randomly play jazz 78s' assistant: directive: 'AudioPlayer.Play' ``` ## What we got ```yaml intent: MusicQuery...
add strass on suggestions. So a user could catch them
Example: https://archive.org/metadata/78_dance-a-little-tanz-a-bissel_rose-gross-maurice-spector_gbia0000577b Request: https://web.archive.org/advancedsearch.php?q=coverage:(*) AND collection:(georgeblood) AND subject:(Yiddish)&fl[]=identifier,coverage,title,year&sort[]=random&rows=2&page=0&output=json should improve it
consider to use this one for automatic testing on a developer side https://github.com/typicode/husky
> USER: play the song landslide from the smashing pumpkins need more information about this steps of dialogs
here is an issue with big projects like us https://github.com/alexa/alexa-skills-kit-sdk-for-nodejs/issues/337 but we could use a workaround with s3.
some JSON responses to `advancedsearch.php` could have tail message `Search engine returned invalid information or was unresponsive`.
PlayCommandIssued [more](https://github.com/alexa/alexa-skills-kit-sdk-for-nodejs#playback-controller-interface)