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

Inquirer.js #9

Open
Sequoia opened this issue Mar 30, 2015 · 4 comments
Open

Inquirer.js #9

Sequoia opened this issue Mar 30, 2015 · 4 comments

Comments

@Sequoia
Copy link
Owner

Sequoia commented Mar 30, 2015

  • Take some input like name, email, age
  • Validation on at least 1 thing
  • print it out formatted some sort of way
@Sequoia
Copy link
Owner Author

Sequoia commented Mar 30, 2015

@grabbou? Still into taking this one on?

@grabbou
Copy link

grabbou commented Mar 31, 2015

Yeah can do! Any suggested ETA on this particular lesson?

@grabbou
Copy link

grabbou commented Mar 31, 2015

I would suggest async operation in the question as well... e.g. user is prompted for the port he wants to use while setting up his let's say Hapi.js set up. Asynchronously we check first available port on the given IP address and provide the result.

@Sequoia
Copy link
Owner Author

Sequoia commented Mar 31, 2015

Yay! 🎉

As for ETA, I hope to have this whole kit & kaboodle in beta release (all lessons written, ready for testing) by about April 10. 😅 Whenever you're free to do it is fine-- if you're not free in that time I may take it on myself.

Regarding Hapi & async port reading etc, I fear that might be too much for this exercise. I'm trying to keep the exercises as narrowly focused on the tool in question as possible & err on the side of "too simple." For example in my tables exercise, I initially required sorting based on a switch, then I decided that was just superfluous & needlessly complicated the lesson so I removed it. Basically, I don't want someone to understand the tool (e.g. inquirer.js) but get stuck because of some other concept.

I err on the side of simple because if worst comes to worst the user just flies thru the exercises quickly, and that's OK!

So the points I'd prefer to hit here are basically all specifically related to inquirer.js:

  • take input
  • validate/reject (make sure age is a number or something)
  • print in some sort of way

It sounds like that's probably simpler than you were planning... is that alright? Lemme know what you think!

@Sequoia Sequoia mentioned this issue Apr 6, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants