[FrameworkBundle] Fix debug:config
& config:dump
in debug mode
#50546
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.
Displaying configs for extensions without a bundle using the
debug:config
&config:dump-reference
commands works depending on whether debug istrue
orfalse
. The reason behind this is the following code:symfony/src/Symfony/Bundle/FrameworkBundle/Command/BuildDebugContainerTrait.php
Lines 42 to 60 in b4128fd
When debug is
true
the extensions are never loaded in the container, so the commands don't work.There are even tests for these cases but they are all executed with debug
false
.This PR aims to make the commands work with both debug
true
&false
. Another problem is that these extensions are not visible in the list of available extensions and are not offered by the completion feature, but since those seem more like new features I've created a separate PR for 6.4: #50548