search

kcmerrill / alfred

(v0.2) Even Batman needs a little help. Task runner. Automator. Build system.
MIT License
63 stars 14 forks source link

Create a test key #19

Closed kcmerrill closed 7 years ago

kcmerrill commented 7 years ago

Lets create a "test" key.

We can tackle this many different ways(open to suggestions) but this would allow each task to test for something before continuing.

Depending on exit code would be then transferred to ok/fail tasks ...

A few ideas:

test: dir.exists whatever test: dir.older 15m test: dir.newer 15m test: app.exists wget

etc etc ...

kcmerrill commented 7 years ago

I originally left this out on purpose, simply because I figured "I'll create a task that would test and then do ok/fail" but the problem with that logic is that it simply complicates the file with a bunch of unneeded tasks.

kcmerrill commented 7 years ago

ok. So this is not done as this specified, but I added a "test" which will simply run a command and depending if the exit code is 1 or 0 will continue on.

kcmerrill commented 7 years ago

This is actually working out better than I ever anticipated. Closing. We can revisit this later.