Allow any case for activity types (#284)

Author: kevgo

documentation/activity-types/cd.md

@@ -6,10 +6,10 @@ that its embedded link or code block points to.
 
 #### Example
 
-Assuming the workspace contains a <a textrun="createDirectory">`foo`</a> directory,
+Assuming the workspace contains a <a textrun="create-directory">`foo`</a> directory,
 you can change into it via this Markdown code:
 
-<a textrun="runMarkdownInTextrun">
+<a textrun="run-markdown-in-textrun">
 ```markdown
 <a textrun="cd">
 Let's change into the [foo](foo) directory.

documentation/activity-types/create_directory.md

@@ -6,9 +6,9 @@
 
 #### Example
 
-<a textrun="runMarkdownInTextrun">
+<a textrun="run-markdown-in-textrun">
 ```markdown
-<a textrun="createDirectory">
+<a textrun="create-directory">
 `directory_name`
 </a>
 ```

documentation/activity-types/create_file.md

@@ -7,19 +7,19 @@
 
 #### Example
 
-<a textrun="runMarkdownInTextrun">
+<a textrun="run-markdown-in-textrun">
 ```markdown
-<a textrun="createFile">
+<a textrun="create-file">
 _test.txt_ with content `foo`
 </a>
 ```
 </a>
 
 - or -
 
-<a textrun="runMarkdownInTextrun">
+<a textrun="run-markdown-in-textrun">
 ```markdown
-<a textrun="createFile">
+<a textrun="create-file">
 
 __test.txt__
 

documentation/activity-types/minimum-node-version.md

@@ -7,7 +7,7 @@ matches what CI servers test against.
 #### Example
 
 Assuming you have a file
-<a textrun="createFile">
+<a textrun="create-file">
 __.travis.yml__ with content:
 
 ```
@@ -19,9 +19,9 @@ node_js:
 
 then you can verify that documentation like:
 
-<a textrun="runMarkdownInTextrun">
+<a textrun="run-markdown-in-textrun">
 ```markdown
-Runs on Node <a textrun="minimumNodeVersion">4</a> or above.
+Runs on Node <a textrun="minimum-node-version">4</a> or above.
 </a>
 ```
 </a>

documentation/activity-types/run_console_command.md

@@ -8,9 +8,9 @@
 - if you just want to verify that your Javascript has no syntax errors,
   use the [validateJavascript](validate_javascript.md) action instead
 
-<a textrun="runMarkdownInTextrun">
+<a textrun="run-markdown-in-textrun">
 ```markdown
-<a textrun="runConsoleCommand">
+<a textrun="run-console-command">
 `​``
 $ echo "hello world"
 `​``
@@ -21,7 +21,7 @@ $ echo "hello world"
 You can enter text into the running command by providing an HTML table
 with the content to enter.
 Assuming we have a little application called
-<a textrun="createFile">
+<a textrun="create-file">
 __greeter.js__
 ```js
 const readline = require('readline');
@@ -36,9 +36,9 @@ rl.question('Your name?', (name) => {
 ```
 </a>
 
-<a textrun="runMarkdownInTextrun">
+<a textrun="run-markdown-in-textrun">
 ```markdown
-<a textrun="runConsoleCommand">
+<a textrun="run-console-command">
 `​``
 $ node greeter.js
 `​``
@@ -61,9 +61,9 @@ and the last one text to enter once the output from the first column has appeare
 Middle columns are ignored.
 `<th>` elements are considered descriptions and are also ignored.
 
-<a textrun="runMarkdownInTextrun">
+<a textrun="run-markdown-in-textrun">
 ```markdown
-<a textrun="runConsoleCommand">
+<a textrun="run-console-command">
 `​``
 $ node greeter.js
 `​``
@@ -102,7 +102,7 @@ If you want to call a command provided by your code base,
 you have to tell TextRunner the path to it.
 As an example, if your code provides an executable called `tool`,
 and it is stored as `public/tool` in your source code,
-<a textrun="verifySourceFileContent">
+<a textrun="verify-source-file-content">
 your __text-run.yml__ needs to contains this section:
 
 ```

documentation/activity-types/run_javascript.md

@@ -2,9 +2,9 @@
 
 To run JavaScript code:
 
-<a textrun="runMarkdownInTextrun">
+<a textrun="run-markdown-in-textrun">
 ```html
-<a textrun="runJavascript">
+<a textrun="run-javascript">
 `​``
 console.log('This is getting executed by TextRunner!')
 `​``
@@ -20,9 +20,9 @@ To make it wait for asynchronous code,
 add the placeholder `<CALLBACK>` where your code would call the callback when its done.
 Example:
 
-<a textrun="runMarkdownInTextrun">
+<a textrun="run-markdown-in-textrun">
 ```html
-<a textrun="runJavascript">
+<a textrun="run-javascript">
 `​``
 const fs = require('fs')
 fs.writeFile('hello.txt', 'hello world', <CALLBACK>)
@@ -33,9 +33,9 @@ fs.writeFile('hello.txt', 'hello world', <CALLBACK>)
 
 
 Alternatively you can also use the placeholder `// ...`
-<a textrun="runMarkdownInTextrun">
+<a textrun="run-markdown-in-textrun">
 ```html
-<a textrun="runJavascript">
+<a textrun="run-javascript">
 `​``
 const fs = require('fs')
 fs.writeFile('hello.txt', 'hello world', function(err) {

documentation/activity-types/start_stop_console_command.md

@@ -10,9 +10,9 @@ and stop the long-running process using a `stopCommand` block.
 
 
 #### Example
-<a textrun="runMarkdownInTextrun">
+<a textrun="run-markdown-in-textrun">
 ```markdown
-<a textrun="startConsoleCommand">
+<a textrun="start-console-command">
 
 `​``
 $ echo Enter your name:
@@ -22,15 +22,15 @@ $ read foo
 
 Wait until it is fully booted up ...
 
-<a textrun="waitForOutput">
+<a textrun="wait-for-output">
 `​``
 Enter your name
 `​``
 </a>
 
 Interact with the server here ...
 
-<a textrun="stopConsoleCommand">
+<a textrun="stop-console-command">
 Stop the current process by hitting Ctrl-C
 </a>
 ```

documentation/activity-types/validate_javascript.md

@@ -4,9 +4,9 @@ This action just checks that JavaScript code contains no syntax errors.
 It is for code blocks that aren't runnable in the context of the tutorial.
 To run Javascript code use the [runJavascript](run_javascript.md) action.
 
-<a textrun="runMarkdownInTextrun">
+<a textrun="run-markdown-in-textrun">
 ```html
-<a textrun="runJavascript">
+<a textrun="run-javascript">
 `​``
 console.log('This is getting executed by TextRunner!')
 `​``

documentation/activity-types/verify_npm_global_command.md

@@ -7,7 +7,7 @@ This action verifies those command names in documenation.
 
 #### Example
 
-<a textrun="createFile">
+<a textrun="create-file">
 Assuming our __package.json__ file looks like this:
 
 ```json
@@ -22,11 +22,11 @@ Assuming our __package.json__ file looks like this:
 then the action below verifies that the instructions describe
 the correct global command name exported by this NPM module.
 
-<a textrun="runMarkdownInTextrun">
+<a textrun="run-markdown-in-textrun">
 ```markdown
 To run this app, call:
 
-<a textrun="verifyNpmGlobalCommand">
+<a textrun="verify-npm-global-command">
 `​``
 $ foo
 `​``

documentation/activity-types/verify_npm_install.md

@@ -8,7 +8,7 @@ that is listed in `package.json`.
 
 #### Example
 
-<a textrun="createFile">
+<a textrun="create-file">
 Assuming our __package.json__ file looks like this:
 
 ```json
@@ -20,9 +20,9 @@ Assuming our __package.json__ file looks like this:
 
 then the action below verifies that the instructions use the correct NPM package name:
 
-<a textrun="runMarkdownInTextrun">
+<a textrun="run-markdown-in-textrun">
 ```markdown
-<a textrun="verifyNpmInstall">
+<a textrun="verify-npm-install">
 `​``
 $ npm i -g my_enormous_package
 `​``