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
chore(logger): streamline logging #10630
Conversation
9a66975
to
d14527b
Compare
Looking good so far, but the build is failing |
hnnng |
d14527b
to
91be438
Compare
Codecov Report
@@ Coverage Diff @@
## master #10630 +/- ##
==========================================
+ Coverage 96.18% 96.3% +0.11%
==========================================
Files 93 93
Lines 9011 8976 -35
==========================================
- Hits 8667 8644 -23
+ Misses 344 332 -12
Continue to review full report at Codecov.
|
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.
🌟
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.
This is a breaking change I am afraid, it will break if someone is using debug
specific logging features.
What are the advantages of this? With debug you can filter out different type of logging. If you want only pool logging you can set DEBUG=sequelize:pool*
etc, is that possible with debuglog
?
I actually went ahead and streamlined all query logging into a single method Please note that it's relatively easy to bring back the |
to me this looks very clean and like the way we want to be headed to. So if you guys feel like this is a breaking change I'd still be up for pushing this for a v6 release instead 🤔 |
I don't think this is breaking btw, in no place sequelize states that it uses |
I'm totally up for merging this, but the build is broken again 😔 |
Heck. |
This is a breaking change and can't be merged. Even if docs are lacking that we support |
Imo the only breaking change is the change in any public documentation or otherwise explicitly exposed format. How would anyone know you can use I have reverted it but please consider documenting the things you want developers to use/know about. |
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.
Unifying query logging logic is a good idea, I have left some suggestions. Other changes for logger class can be reverted
…h sequelize.logQuery
Boiled it down a little, the |
… through sequelize.logQuery
…logging through sequelize.logQuery
Disregard that, needs more work, will be another PR. |
…nel all logging through sequelize.logQuery" This reverts commit 5fd9078.
…): channel all logging through sequelize.logQuery"
…logging): channel all logging through sequelize.logQuery"
…! feat(logging): channel all logging through sequelize.logQuery"
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.
👍
🎉 This PR is included in version 5.2.11 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Rename postgresql query debug namespace (mistake in #10630)
Pull Request check-list
Please make sure to review and check all of these items:
npm run test
ornpm run test-DIALECT
pass with this change (including linting)?Description of change
Replaces
debug
package withdebuglog
native and acts as a foundation for #10284 (comment)cc @javiertury
#Fixes 10661