-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[2.7] Some parameters are not loaded #15238
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
Comments
Does the error remain if you use this other config? # ...
parameters:
'my-parameter': 123 |
@javiereguiluz Yes, the error remains. |
@Azenet Could you fork the the Symfony Standard Edition an make the minimum set of needed changes to reproduce your issue? |
@Azenet Thank you for providing the fork. I can confirm that this does not work with Symfony 2.7. It even does not work with Symfony 2.6.9. |
Okay, I had a closer look at this and the "issue" simply is that you define the |
by the way, see also https://github.com/symfony/symfony/blob/2.8/UPGRADE-2.5.md#yaml-component |
@xabbuh Thanks, I missed this change. |
Hi,
I used to have (with Symfony 2.6) parameters in app/config/config.yml in this form :
I was able to access these using
ContainerInterface->getParameter('my-parameter');
, however this now throws an InvalidArgumentException with the message "The parameter "my-parameter" must be defined." starting from Symfony 2.7.There's no trace of this change in the change log nor in the UPGRADE-2.7.md file, is this a bug or is this new behavior intended ?
Thanks.
The text was updated successfully, but these errors were encountered: