-
Notifications
You must be signed in to change notification settings - Fork 305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config - incompatible function signatures #1102
Comments
…\Dflydev\DotAccessData\Data
This is fixed in dev-main of consolidation/config. I think you need to be using a non-stable version of grasmash/expander to be affected. |
I am using the latest commit from the consolidation/config. Which is the fde7dfe 2.x-dev is a branch alias in the composer.json |
Before the upgrade everything worked fine. consolidation/config
consolidation/robo grasmash/expander
I am not referencing directly the grasmash/expander in my composer.json. {
"require": {
"consolidation/config": "2.x-dev",
"consolidation/robo": "3.x-dev"
}
}
|
|
I thought fde7dfe fixed this. Will need to investigate. |
Oh I see the same bug exists in Robo's override of the config class. |
Steps to reproduce
\Robo\Robo::createConfiguration()
calls the
new \Robo\Config\Config();
constructor without argument.$data = null
But the
\Dflydev\DotAccessData\Data::__construct
does not accepet NULL.Expected behavior
No fatal error
Actual behavior
The text was updated successfully, but these errors were encountered: