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
fix(logging): Added check for log level value #13941
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Call validateLogLevel()
from the main code, and let that function log and exit if the value is invalid. Otherwise continue
…ogLevelCheck # Conflicts: # lib/logger/index.spec.ts # yarn.lock
@hasanwhitesource in future it's preferred that you keep the same PR, so that you create less noise for everyone else. Now, every comment made before will be lost and not transferred to your new PR. Worst case keep the same PR but force push your changes from a clean branch locally. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does Bunyan accept both upper and lower case? If not, are you doing any massaging of the string?
Yes it works with all lower case or all uppercase characters |
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Also trim Co-authored-by: Rhys Arkins <rhys@arkins.net>
@viceice Are there anymore changes that need to be done you think? |
🎉 This PR is included in version 31.68.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Changes:
Renovate will now check if the log level from the config is a valid bunyan logLevel value and will log error and then stops running.
Context:
Documentation (please check one with an [x])
How I've tested my work (please tick one)
I have verified these changes via: