package.json
since this can specify the entry point if it’s not index.js
which is the default.
package.json
since this can specify the entry point if it’s not index.js
which is the default.
The basic idea is that when creating the “intent”, i.e. the action that you want Alexa to do, you also define “slots”. The slots are the variables; if this were a command line tool, they’d be the arguments you typed. It’s possible to include both intent and slots in your wording when you speak to Alexa, but equally you can just invoke the skill and have it prompt you for the rest of the information. Continue reading
GitHub has brilliant advanced search functionality, and what I wanted was:
is:pr commenter:lornajane sort:updated-desc
Which gives me a list of all the pull requests I’ve commented on, with the most recent first. I couldn’t remember the exact repo name and I also often switch is:pr
for is:issue
as appropriate, but this search string has been very helpful for finding those odd things you want to follow up on.
Do you have a favourite GitHub search string combination? Would you care to share it in the comments? Thanks :)
There are a bunch of good resources around for setting up skills, picking the name, configuring the “invocation” which is what to say to make the code happen, and so on. I’ll skip this section and instead just share a couple of tutorials that I rely on a lot:
Once your skill is configured, it’s time to write the code (note: UK users need to pick English (UK) and not English (US) as otherwise your skill will mysteriously fail in your home region. Guess how I learned that??) Continue reading
wsk activation list -l1 | tail -n1 | cut -d ' ' -f1 | xargs wsk activation logs
From left to right, sections separated by the pipe |
character, this is what happens:
Of course it’s wrapped up in a script so I just run that from the commandline and check where I went wrong this time …
node-modules
folder, try this:
grep -R --exclude-dir node_modules [what to search for] *
If you’re using a different tech stack you may want to exclude a different directory (for PHP, the directory would be called vendor
), but this is a very handy tip and a bit nicer than the older approach I was using which did the whole search and then used a second grep to eliminate things by using the -v
switch.