Environments config is confusing

[cviebrock]

// The environments in which Flatten should not run
'environments' => array(),

That seems a bit counterintuitive. A config option named environments sound like it should define the env(s) where Flatten would run, not where it's ignored.

Even though it would break BC, would you consider flipping the logic, so environments defines where you want it to run ... or alternatively, rename the config option ignore_environments?

[willrowe]

Wouldn't it be cleaner if instead of an environments option there was an enabled option? This would take advantage of the existing environment configuration in Laravel. If you don't want it to run in a certain environment, just create the corresponding folder/file and add 'enabled' => false.