Default init path to CWD (like NPM init) about zapier-platform-cli HOT 5 CLOSED

Closing for #30.

from zapier-platform-cli.

I'm not a huge fan of this - as it could clobber your working directory. npm has a lot of "inbuilt" knowledge of it being used in the working directory. Compare that to pip which is all about the current virtualenv (and doesn't care at all about working directory).

from zapier-platform-cli.

Still I think since these apps are NodeJS and even more because the command is "init" (not "create") it makes sense to follow existing patterns in that ecosystem.

But if we don't, then at least the command should fail right away IMHO since with this much output before the error, it's easy to miss - in particular in a B/W console.

from zapier-platform-cli.

I am really uncomfortable with the level of setup we do (creating files, folders, etc.) without an explicit location argument.

Maybe we don't print help right away but suggest it? Definitely cluttered as is and hides the error message.

from zapier-platform-cli.

Let's clean it up then, since in particular the last line of help is confusing if it's printed just before the error. You could think it actually did finish:

# Finished! You might need to npm install then try zapier test!

Errors running command `zapier init`:

!!!   Missing required positional argument 1/location

I'd prefer:

$ zapier init
Error: Missing required argument 'path'

Run `zapier help init` for usage.

$

from zapier-platform-cli.