Adding a `:unless` option to a Slop::Option about slop HOT 4 CLOSED

I don't think there is any harm in collecting that data, it doesn't harm my use case and may prove useful for others.
I'm not touching opts[:head] or opts[:tail] in grep, i don't expect them to be set and have no interest in their value, but who knows what other people might use this feature for.

from slop.

I thought Slop was for gathering data from command line options, not a framework for building CLIs..?

from slop.

@c00lryguy Whilst that's true, each command can of course have its own execution block. There are plenty of times where one might want to omit the execution of this block, specifically depending on if another option is used. I completely agree that Slop should continue to collect data and perhaps solely ignore the block.

EDIT: I should also add that there is no magic happening with this code. The :unless flag is simply checking if an option is available in the arguments passed to Slop.new this ensures Slop stays below 500 lines

from slop.

DIff is available here. Closing this issue. Discussion can continue if you have anything to add.

Thanks for the comments

from slop.