bignerdranch/developing-alexa-skills-solutions

Channel for course discussion and questions (requires github or Twitter account)

developing-alexa-skills-solutions's Issues

4_Persistance - The response is invalid when trying to 'load madlib'

Getting this response even when trying to upload the ready to go solution code (after commenting :13 and uncommenting :15) and following all the config/IAM role directions found @ https://gist.github.com/unitygirl/3b0bdc0f0826fb88448cf17ac4a7293b

5_Linking Accounts - wrong link for OAuth1.0a server source

Tutorial pdf directs you to https://github.com/bignerdranch/alexa-airportinfo to view server source but it really lives at https://github.com/bignerdranch/alexa-account-linking-service

Responses not coming through

Heads up for anybody using this guide, Alexa-app has been updated so if you're having issues with the responses not coming back, but can see them being logged out, check out this link that explains how to fix it. alexa-js/alexa-app#210

PDF Page 23 Error on no delay return template

On Chapter 2, page 23 FAADataHelper.prototype.formatAirportStatus if.. else.. block else return template there was an extra underscore in the return template(). Screenshot of actual working code vs. PDF attached. Thanks.

Error is thrown if following Chapter 2 tutorial instructions

In the coursebook, on page 34, above Figure 2.13 there is an instruction to:

advance to the configuration page.

Following this instruction will result in an error unless the following step "Defining the Custom Slot Type" is performed first.

From a student's perspective, this is a confusing flow, and I feel it would be benficial if we were instructed on defining the custom slot type before moving on to the configuration page.

tftAccountLinking_Chapter.pdf contains broken code

There are some out of scope issues with this pdf and how it shows you should utilize the twitter helper - i.e. it puts var twitterHelper declare inside the if (_.isEmpty(airportCode)) check - which will throw an undefined exception via lambda/whatever else when run. Final solution code differs and should work.

Confusing use madlibHelperData placeholder

I found this placeholder confusing. Specifically, I didn't realize it was a placeholder until the following section. I spent a few minutes looking around the code in index.js, in madlib_helper.js, etc, looking for where this was defined. After checking with a colleague I was directed to just push forward and saw the replacement of that with a call to getMadlibHelper(request);.

Perhaps naming this placeholder to suggest the block of code is not runnable. Or just leave it out, as it can't be run in that state.

Capitalization issue in PDF, module 1

The capitalization of GreeterService in the PDF snippet does not match the case in the answer.

From PDF:

exports.handler = function(event, context) {
 var GreeterService = new GreeterService();
 GreeterService.execute(event, context);
};

From 1_helloAlexa/solution/greeter/src/index.js (line 21)

exports.handler = function(event, context) {
  var greeterService = new GreeterService();
  greeterService.execute(event, context);
};

var assignment error in PDF, module 2

Page 23 in PDF has the following code:

     //no delay
     var template = _.template('There is currently no delay at ${airport}.');
     return _.template({ airport: aiportStatusObject.name });

Should be:

    //no delay
    var template =_.template('There is currently no delay at ${airport}.');
    return template({ airport: aiportStatusObject.name });

Note not returning lodash template, but instead using the actual template var.