configuration & php artisan config:cache : bug

[Grummfy]

Q	A
Bug?	no (for me laravel is bad on this) & yes (because no choice)
New Feature?	no
Framework	Laravel (Lumen?)
Framework version	5.4
Package version	4.1
PHP version	*

Actual Behaviour

When I use php artisan config:cache, the app crashed.

Expected Behaviour

When I use php artisan config:cache, i would like my app still running.

Steps to Reproduce

install the package with the config file, and run php artisan config:cache

Possible Solutions

Ask them to make closure usable with laravel config?
Until that
implements a OwenIt\Auditing\Contracts\UserResolver with the same content as the closure

More information: laravel/framework#9625
I totally disagree with the comment that config with closure is bad, but for now there is no good solution for it.

[quetzyg]

What exactly is your point with this issue?

[Grummfy]

well because by default the configuration file came with a closure, you can't cache the config (make the app crash). So just update the default config with a default implementation of the resolver in a class.

[quetzyg]

While having a closure in the configuration won't work once you try to cache, it makes working with the package a bit quicker, having one less thing to worry about at the beginning. Also, the issue is documented in the troubleshooting and settings sections, along with a few issues here on GitHub (#213, #234, #237, #250, #284).

I'll keep this one open, to remind me to add a comment about it in the configuration file.

[Grummfy]

well I forget to check the troubleshooting guide ;)
too fast post this issue

[mikebronner]

I would like to support the idea that this should be fixed. The configuration file should not cause artifacts or errors working with default Laravel functionality.

[quetzyg]

A Closure is no longer set as the default resolver in the configuration.

[mike23v]

Hi @quetzyg,
I'm having the following error Illuminate\Database\Query\Builder::check() since you removed the Closure as a default resolver in the configuration or in config/audit.php. Can you please help me on this.? Thanks

[quetzyg]

@mike23v, the Illuminate\Database\Query\Builder::check() issue is because you're doing it wrong. I have already addressed that in the issue you opened (#316).