-
Notifications
You must be signed in to change notification settings - Fork 203
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
EZP-30547: As a Developer I'd like to be able to debug config resolver & services #2635
Conversation
25a5e9a
to
a4dd59a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I needed very similar command while working on last demoed feature so +1 from my side.
eZ/Bundle/EzPublishCoreBundle/Command/DebugConfigResolverCommand.php
Outdated
Show resolved
Hide resolved
eZ/Bundle/EzPublishCoreBundle/Command/DebugConfigResolverCommand.php
Outdated
Show resolved
Hide resolved
0b905b7
to
fd68caa
Compare
@adamwojs Updated FYI: I assumed you implied it should now be on it's own line given we use dump |
eZ/Bundle/EzPublishCoreBundle/Command/DebugConfigResolverCommand.php
Outdated
Show resolved
Hide resolved
eZ/Bundle/EzPublishCoreBundle/Command/DebugConfigResolverCommand.php
Outdated
Show resolved
Hide resolved
fd68caa
to
eaf629c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like these new commands, well done!
Just a two small nitpicks:
eZ/Bundle/EzPublishCoreBundle/Command/DebugConfigResolverCommand.php
Outdated
Show resolved
Hide resolved
eZ/Bundle/EzPublishCoreBundle/Command/DebugConfigResolverCommand.php
Outdated
Show resolved
Hide resolved
Thanks @kmadejski 👍 😃 |
eZ/Bundle/EzPublishCoreBundle/Command/DebugConfigResolverCommand.php
Outdated
Show resolved
Hide resolved
eZ/Bundle/EzPublishCoreBundle/Command/DebugConfigResolverCommand.php
Outdated
Show resolved
Hide resolved
eZ/Bundle/EzPublishCoreBundle/Command/DebugConfigResolverCommand.php
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi. Sorry for a long delay.
About #2635 (comment) - ok, but maybe let's split it to a separate PR? It might require tweaking for Symfony4 as it would become not much usable.
eZ/Bundle/EzPublishCoreBundle/Command/DebugConfigResolverCommand.php
Outdated
Show resolved
Hide resolved
Co-Authored-By: Kamil Madejski <kmadejski@live.com>
662e8f0
to
13fd589
Compare
@alongosz Updated, command is now a service Same goes for you @mateuszbieniek, your remarks should be solved by now. |
Need this in helping debug some on-going config resolver issues on multi site config setup, so merging for testing to be done pre-release with the other relevant config resolver changes to help detect these issues. |
6.7
(given these can be useful for support)Commands to be able to debug config resolver and services, as used on #2634 to verify that issue was not config resolver but rather early loaded service.
Useful both for debug (especially in support case) use cases, but also for doc / training use cases to verify configuration steps have been completed ok.
TODO:
$ composer fix-cs
).