Closed vlasscontreras closed 4 years ago
The current one works fine for me on a clean Laravel installation:
Please, provide the steps to reproduce the issue.
If affects projects with cached config entries, reproducible with the following flow:
laravel new app && cd app
php artisan config:cache
composer require akaunting/firewall
Then your workflow is wrong, you should first install firewall then cache config.
Not all projects start having this package because it could have been discovered even after going to production and is most likely to have cached config. That's why I suggested this change.
Anyway, thank you for your feedback.
Prevent errors during installation due the config value being
null
before publishing config files.