I'm submitting a...

• Bug report
• Feature request
• [x ] Documentation issue or request
• Other... Please describe:

We have an intent with a custom slot called topic. The values of this slots could be for example:

Sports, Science, Cinema, TV
So our sample Utterances are like this:
{topic}
tell me about {topic}
what

I have several questions, hopefully the output of this is I can submit a PR for some doc updates:

1. the node-sonos-http-api allows for a folder named presets in it (for organization purposes) and it is the preferred way so perhaps we should update accordingly (I believe it even hot loads them / don't have to restart the server when you add new json files to presets folder)
2. When I have a .j

I have an setup running with docker and an LE certficate. If you want I could patch up some docs for it (also with htaccess vhost configuration, to proxy it to the dockers ip (+ port forwarding)

The documentation for deploying to Heroku here shows an out of date Procfile example. The correct Procfile should be:

web: bundle exec puma -C config/puma.rb
sidekiq: bundle exec sidekiq -C config/sidekiq.yml -q stealth_webhooks -q stealth_replies -r ./config/boot.rb

This is one of the breaking changes for version 1.1.0

I've been trying to setup an Alexa bot that talks to Azure without success. First I tried to deploy the sample project but I kept running into exceptions being thrown by the Logger.

After removing the Logger from the application I finally managed to get something working.

However, whenever I try to type start skill in the Test Console I keep getting that an error:

There was

When outputting sample utterances and the enhancements from #3, we need to link to documentation with screenshots on how to set this up in the amazon interface

I was expecting that aws sdk picks up the current profile that I configure with aws configure but it actually doesn't and requires to set environment variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.

Would be great to update the README and also maybe add else option into the catch block of iam.getUser in create-iam.js.

The RequestValidator in not complete under unit tests. It's not that easy because of openssl connects.

Referrs to:
alexaTest.getIntentRequest(intentName, [slots], [locale])

AMAZON.DATE returns "undefined" (contrary to other slot types returning "?"), if no or wrong slot value has been provided in the input. There is no way without hacks to simulate this behavior in the test framework.

Currently en_US and en_GB use the version 1 intents schema (see #23, #61) but French and German are still using v0.

Users should be given a high level overview of functionality they can trigger when activating the LaunchIntent for the first time (currently they only get this information in the reprompt).

I have a small change that I can open a PR for if I can push my branch to this repo.

The Flask-Ask link is changed to go to the readthedocs site for Flask-Ask, and the link to John Wheeler goes to his Github.