Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[FrameworkBundle] Throw for missing container extensions#17486
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
Closed
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
This covers cases when a bundle does not have an extension, whichlead to FatalErrorException with ```Call to a member function getAlias() on null```
Contributor
linaori commentedJan 22, 2016
Looks good to me 👍 |
Member
fabpot commentedJan 25, 2016
Thank you@kix. |
fabpot added a commit that referenced this pull requestJan 25, 2016
…kix)This PR was submitted for the master branch but it was merged into the 2.7 branch instead (closes#17486).Discussion----------[FrameworkBundle] Throw for missing container extensions| Q | A| ------------- | ---| Bug fix? | yes| New feature? | no| BC breaks? | no| Deprecations? | no| Tests pass? | yes| Fixed tickets | none| License | MIT| Doc PR | noneThis covers the case when an existing bundle does not have an extension, and its config is dumped. Before, calling `app/console config:dump` on such bundle lead to FatalErrorException with ```Call to a member function getAlias() on null```, now we process such cases and throw an exception with some explanatory text.Commits-------884368e Throw for missing container extensions
ContributorAuthor
kix commentedJan 25, 2016
Thanks for the merge! |
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.
This covers the case when an existing bundle does not have an extension, and its config is dumped. Before, calling
app/console config:dumpon such bundle lead to FatalErrorException withCall to a member function getAlias() on null, now we process such cases and throw an exception with some explanatory text.