You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the default behavior, SemanticLogger will add a File Appender and an IO appender. The ap_options to configure awesome print are only used to configure the File Appender:
I would expect ap_options to be used in the IO Appender, since it's more common people look at the logging in a terminal instead of tailing log/development.log
Actual Behavior
The ap_options are only used to configure the File Appender:
My guess that that the IO is included by default in SemanticLogger, but I'm not very familiar with the source code. It seems IO Appenders are explicitly not reconfigured to use the updated formatter:
Environment
Ruby: 3.1.2
Rails: 7.0.3.1
Semantic Logger: 4.11.0
Rails Semantic Logger: 4.10.0
Expected Behavior
Using the default behavior, SemanticLogger will add a File Appender and an IO appender. The ap_options to configure awesome print are only used to configure the File Appender:
rails_semantic_logger/lib/rails_semantic_logger/engine.rb
Line 53 in c94ae1f
I would expect
ap_options
to be used in the IO Appender, since it's more common people look at the logging in a terminal instead of tailing log/development.logActual Behavior
The ap_options are only used to configure the File Appender:
Config:
Semantic logger configuration:
Pull Request
My guess that that the IO is included by default in SemanticLogger, but I'm not very familiar with the source code. It seems IO Appenders are explicitly not reconfigured to use the updated formatter:
rails_semantic_logger/lib/rails_semantic_logger/engine.rb
Line 64 in c94ae1f
The text was updated successfully, but these errors were encountered: