Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[DependencyInjection][CheckTypeDeclarationsPass] Always resolve parameters#37193
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
nicolas-grekas approved these changesJun 11, 2020
Member
fabpot commentedJun 11, 2020
Thank you@fancyweb. |
Contributor
alexander-schranz commentedJun 11, 2020
@fancyweb Thank you also from my side 👍🏼 |
fabpot added a commit that referenced this pull requestJun 12, 2020
…resolved parameters pointing to environment variables (fancyweb)This PR was merged into the 4.4 branch.Discussion----------[DependencyInjection][CheckTypeDeclarationsPass] Handle unresolved parameters pointing to environment variables| Q | A| ------------- | ---| Branch? | 4.4| Bug fix? | yes| New feature? | no| Deprecations? | no| Tickets | -| License | MIT| Doc PR | -Follow up to#37193Unresolved parameters pointing to environment variables can be added to definitions after ResolveParameterPlaceHoldersPass execution. It is the case in the initial reported bug (RegisterListenersPass is executed after ResolveParameterPlaceHoldersPass). In this case, the parameter value is an env placeholder, so we need to try to resolve it.Commits-------dac3c8f [DependencyInjection][CheckTypeDeclarationsPass] Handle unresolved parameters pointing to environment variables
This was referencedJun 12, 2020
Merged
Merged
Merged
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading.Please reload this page.
This is true only when the XML debug container is used, not on a live container that can contain unresolved parameters in the
%my_param%form. That was my mistake. We have to resolve to get the parameter type.$value = [];was just an improvement to avoid useless parameter resolve btw.