This PR was merged into the 2.6-dev branch.
Discussion
----------
[FrameworkBundle] container:debug : list services if no service match exacly the name argument
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | yes
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #11303
| License | MIT
| Doc PR |
If we launch the command "container:debug log" and there is no
service nammed log, it will print something like this :
```
[0] logger
[1] monolog.handler.console
[2] monolog.handler.debug
```
After the service has been chosen, usual container:debug informations
are displayed.
Commits
-------
16201b6 [FrameworkBundle] container:debug : list services if no service match exacly the name argument
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | yes
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #11303
| License | MIT
| Doc PR |
If we launch the command "container:debug log" and there is no
service nammed log, it will print something like this :
```
[0] logger
[1] monolog.handler.console
[2] monolog.handler.debug
```
After the service has been chosen, usual container:debug informations
are displayed.
This command uses a new container pass which dumps the ContainerBuilder into a cache file by serializing it. It's possible that we don't want this to run when kernel.debug = false, but I don't see the harm of generating the file and running the container:debug in, for example, the prod environment seems to make sense.