You may be wondering where all that amazing debugging information went in your ColdBox 4.0 application. Have no fear. You can still have your cake and eat it too. We modularized it (sensing a theme in ColdBox 4.0 yet?) So, how do you get all that wonderful debugging info?
Easy! Using CommandBox, run the following command.
box install cbdebugger --saveDev
Notice the --saveDev we added to our command. This is handy as it tells CommandBox that you only want this as a dependency for your application in development.
Once the debugger module is installed, you can control the settings via the debugger structure in your main Coldbox config file.
Also, if you need access to the debugger service or the timer, they are available via the following WireBox mappings.
- debuggerService@cbdebugger
- timer@cbdebugger
Just call getInstance() on either to snag them as needed.
Debug to your heart's content.
.png)
We are pleased to announce the general availability of CommandBox 5.9.1. This is a very small release with two changes.
Add Your Comment
(2)
Feb 11, 2015 18:16:55 UTC
by Jim Priest
If you are like me and just getting started with ColdBox - once you have installed the debugger module, look under /modules/cbdebugger/readme.md and there is an example 'Debugger Settings' of what you need to copy to your ColdBox config file to enable things.
Feb 27, 2015 00:03:15 UTC
by Dan O'Keefe
I get "command cannot be resolved". Isn't it supposed to just be "install cbdebugger --saveDev"?