Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

node-debug-school help is not correct for verify and run subcommands #4

Open
misterdjules opened this issue Oct 1, 2014 · 0 comments
Assignees

Comments

@misterdjules
Copy link
Contributor

Here's the output from node-debug-school help:

[root@b0620154-649f-6d1b-c344-eaa9f0df47af ~]# node-debug-school help
Usage

  node-debug-school
    Show a menu to interactively select a workshop.
  node-debug-school list
    Show a newline-separated list of all the workshops.
  node-debug-school select NAME
    Select a workshop.
  node-debug-school current
    Show the currently selected workshop.
  node-debug-school print
    Print the instructions for the currently selected workshop.
  node-debug-school reset
    Reset completed workshop progress.
  node-debug-school run program.js
    Run your program against the selected input.
  node-debug-school verify program.js
    Verify your program against the expected output.

[root@b0620154-649f-6d1b-c344-eaa9f0df47af ~]#

It states that the run and verify subcommands both expects a file name representing a JavaScript program as their only argument, whereas the workshop sometimes expect a value (a number for instance) or a file name that represents something else (e.g: a text file).

It could be that expecting students to provide answers to exercises that are not programs written in JavaScript is not how workshopper is supposed to be used. On the other hand, it seems legitimate to be able to create exercises that accept other types of answers.

We should determine if changing the help command's output can be done in a sane way to account for some variations in the types of answers. If not, we could ask students to write their simple answers in simple JavaScript programs like:

console.log(42)

for an exercise that expects an answer that is a number, but it seems overkill.

The last option would be to rethink the workshop so that writing solutions as JavaScript programs always makes sense.

@misterdjules misterdjules self-assigned this Oct 1, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant