Skip to content
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

Merged
merged 4 commits into from
Jun 18, 2019

Conversation

andrerom
Copy link
Contributor

@andrerom andrerom commented May 11, 2019

Question Answer
JIRA issue EZP-30547
Bug/Improvement yes
Target version 6.7 (given these can be useful for support)
BC breaks no
Tests pass yes
Doc needed Probably yes

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:

  • Implement feature / fix a bug.
  • Implement tests.
  • Fix new code according to Coding Standards ($ composer fix-cs).
  • Ask for Code Review.

@andrerom andrerom changed the base branch from master to 6.7 May 11, 2019 20:00
@andrerom andrerom force-pushed the config_debug_commands branch from 25a5e9a to a4dd59a Compare May 11, 2019 20:01
Copy link
Member

@adamwojs adamwojs left a 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.

@andrerom andrerom force-pushed the config_debug_commands branch 4 times, most recently from 0b905b7 to fd68caa Compare May 21, 2019 07:32
@andrerom
Copy link
Contributor Author

andrerom commented May 21, 2019

@adamwojs Updated
Screenshot 2019-05-21 at 09 38 13

FYI: I assumed you implied it should now be on it's own line given we use dump

@andrerom andrerom force-pushed the config_debug_commands branch from fd68caa to eaf629c Compare May 21, 2019 11:39
Copy link
Member

@kmadejski kmadejski left a 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:

@andrerom
Copy link
Contributor Author

Just a two small nitpicks:

Thanks @kmadejski 👍 😃

Copy link
Member

@alongosz alongosz left a 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.

@andrerom andrerom force-pushed the config_debug_commands branch from 662e8f0 to 13fd589 Compare June 5, 2019 12:21
@andrerom
Copy link
Contributor Author

andrerom commented Jun 5, 2019

@alongosz Updated, command is now a service

Same goes for you @mateuszbieniek, your remarks should be solved by now.

@andrerom
Copy link
Contributor Author

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.

@andrerom andrerom merged commit 5019949 into 6.7 Jun 18, 2019
@andrerom andrerom deleted the config_debug_commands branch June 18, 2019 08:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

5 participants