You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When publishing all configuration files the stub for app.php does not contain all used keys.
Should the stubs contain everything that is required?
I found this issue because I am using the new dontMergeFrameworkConfiguration() app setting.
To use this setting I believe you must publish all config files and maintain them yourself.
But once you have done that you get errors as there are missing config keys.
if you run composer install after publishing all config files and using the setting dontMergeFrameworkConfiguration(), this error is produced.
In RegisterProviders.php line 59:
array_merge(): Argument #1 must be of type array, null given
Laravel Version
11.1.1
PHP Version
8.2.13
Database Driver & Version
No response
Description
When publishing all configuration files the stub for app.php does not contain all used keys.
Should the stubs contain everything that is required?
I found this issue because I am using the new
dontMergeFrameworkConfiguration()
app setting.To use this setting I believe you must publish all config files and maintain them yourself.
But once you have done that you get errors as there are missing config keys.
if you run
composer install
after publishing all config files and using the settingdontMergeFrameworkConfiguration()
, this error is produced.The below repository is a new Laravel install with all config published that shows it errors when running
composer install
https://github.com/MaxGiting/publish-config-example
Steps To Reproduce
composer create-project laravel/laravel publish-config-example
php artisan config:publish --all --force
dontMergeFrameworkConfiguration()
MaxGiting/publish-config-example@ced8045composer install
The text was updated successfully, but these errors were encountered: