JMSDebuggingBundle
JMSDebuggingBundle copied to clipboard
schmittjoh
This bundle provides advanced debugging tools for your Symfony2 project.
Apologies if this is documented somewhere else, but I cannot seem to find information anywhere on how to get the Help Resources portion of a 500 error page to show...
see https://github.com/schmittjoh/composer-deps-analyzer basically showing the deps graph inside the profiler UI can reuse the JS graph library used for the DIC visualization
I have detected minor typing errors in your css-files: error_reporting.css: # jms-debugging-error-reporting uses margin-bottm ilo margin-bottom # jms-ui-report-dialog-attr uses font-color ilo color
Currently, the max level of the DIC visualizer is [hardcoded in the JS code](https://github.com/schmittjoh/JMSDebuggingBundle/blob/master/Resources/js/dic_visualizer_init.js#L18). It would be great to be able to change in through the UI.
When using the profiler offline, the GA tracker is not available which breaks the code of the DIC panel here: https://github.com/schmittjoh/JMSDebuggingBundle/blob/master/Resources/js/app/dic_visualizer.js#L124 IMO, it should be possible to use the profiler...
Add heuristics to show common entry points into the service graph (which services are requested first, and what other services causes that to load, etc.)
Graph scaling needs to be improved to better use the available space. Right now, the graph often requires too much space for too few nodes. Possible approaches: - count line...
Service details like its definition, where it is defined, etc. should be shown (possibly as context menu item).
Certain changes that the compiler makes like removing definitions, inlining definitions, etc. should be shown.
The visualizer should show if a definition inherits from another definition.
Metadata
Owner
Metadata
This bundle provides advanced debugging tools for your Symfony2 project.