Direct console debugging is left in the AbstractAppender and FileAppender
Description
There is one instance in the fileAppender and 3 instances in the AbstractAppender where calls to the low-level out() method have been left in.
Ex:
These calls bypass LogBox and cannot be configured or turned off. There are some instances of the err() method still in use, but I'm ok with those since they represent an error scenario and wouldn't fill up the logs as part of normal operation.
We should comment out the out() messages in stable releases, or re-configure them to use LogBox so they can be controlled. Otherwise, a ColdBox app operating normally creates a lot of noise in the console that can't be controlled.
Activity
Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.
There is one instance in the fileAppender and 3 instances in the AbstractAppender where calls to the low-level out() method have been left in.
Ex:
These calls bypass LogBox and cannot be configured or turned off.
There are some instances of the err() method still in use, but I'm ok with those since they represent an error scenario and wouldn't fill up the logs as part of normal operation.
We should comment out the out() messages in stable releases, or re-configure them to use LogBox so they can be controlled. Otherwise, a ColdBox app operating normally creates a lot of noise in the console that can't be controlled.