-
Notifications
You must be signed in to change notification settings - Fork 247
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
Move #warn
calls from Kernel to Logger
#572
Comments
我已收到你的邮件,谢谢!
|
Well, they are different in that I notice the code is using I wonder if we should make this warning explicitly disablable? |
@ColinDKelley It seems that people having this issue will be able to configure listen in a rails initializer too right? |
@AlexB52 Thanks! That style of configuration was an inspiration from Rails configs that work like that. Let's keep the discussion happening over on that PR. |
Resolved in v3.9.0. See README for documentation. |
This issue guard/listen#572 has been resolved.
This issue guard/listen#572 has been resolved.
This issue guard/listen#572 has been resolved.
This issue guard/listen#572 has been resolved.
I'm looking to silence the Symlink error.
People have mentioned you can monkey patch
Listen::Record::SymlinkDetector
class: rails/webpacker#1990I see that
logger
has a warn level that can be set, but some warn messages are made by Kernelkernel warn references:
Are there specific reasons for using
Kernel#warn
instead ofLogger#warn
?Can we move the calls from
Kernel
toLogger
?The text was updated successfully, but these errors were encountered: