Would it be possible to use filter instead of whitelist? about laravel-console

[darsain]

If I understand correctly, you want there to be a console::console.filter config with a value of whitelist that would be used in:

Route::group(array('before' => Config::get('console.filter', Config::get('console::console.filter'))), function () {
    // routes
})

so you could replace it with your own, right?

[crynobone]

It is possible, however configuration would be lost after upgrade :)

Mior Muhammad Zaki
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)

On Sunday, October 28, 2012 at 6:38 PM, Darsain wrote:

If I understand correctly, you want there to be a console::console.filter config with a value of whitelist that would be used in:
Route::group(array('before' => Config::get('console.filter', Config::get('console::console.filter'))), function () { // routes })

so you could replace it with your own, right?

—
Reply to this email directly or view it on GitHub (#1 (comment)).

[darsain]

And that's why all config is loaded from console.option, and falls back to console::console.option (as it is illustrated in my code snippet above). If you are changing the config in bundles/console/config/console.php
, read the config documentation section that explains how to change the config and keep it there regardless of upgrades.

And is this what you are asking for anyway? I'm not sure if I understand you, because Would it be possible to use filter instead of whitelist? doesn't make sense, as whitelist IS a filter.

So let me rephrase: Are you asking to have an option to use a CUSTOM filter for console routes? I.e. the very thing illustrated in my code snipped above?

[darsain]

I hope this solves your problem. But be aware that having this bundle on production servers is dangerous.