-
Notifications
You must be signed in to change notification settings - Fork 134
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
Comments
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. |
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. |
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. |
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!
The text was updated successfully, but these errors were encountered: