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

Add debug command #327

Closed
umulmrum opened this issue Jul 10, 2020 · 4 comments · Fixed by #527
Closed

Add debug command #327

umulmrum opened this issue Jul 10, 2020 · 4 comments · Fixed by #527

Comments

@umulmrum
Copy link
Contributor

Hi,

it would be great to have a debug command like e.g. Symfony has for routing or config. Not sure what exactly this command should show, but what I hope for is a way to see which classes are in which layer(s) so that flaws in the depfile can be found more easily.

Thanks!

@smoench
Copy link
Contributor

smoench commented Jul 14, 2020

Hi, I think there are two possibilities. One would be a list of all classes grouped by the layer (might be hard to read). The other would show the layers for one class.

@umulmrum
Copy link
Contributor Author

Why not both? :-)

You're right, the list of classes by layer can be huge, but output can still be redirected to a file and inspected there. This way we can see if a layer contains the correct files or is even empty. Checking this for each class separately would be really cumbersome.

@smoench
Copy link
Contributor

smoench commented Jul 20, 2020

Both are possible ;-)

For now you can try the junit output formatter. There are all dependencies be written. With a plug-in for your ci you might get a nicely overview.

@smoench
Copy link
Contributor

smoench commented Mar 26, 2021

@umulmrum I prototyped a possible solution in #527. WDYT?
In the build artifacts you will find a phar-file.

@smoench smoench added this to the 0.13.0 milestone Apr 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants