-
Notifications
You must be signed in to change notification settings - Fork 153
feat(logger): change visibility to protected #3377
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
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.
I see that you changed more methods and properties than the ones we discussed in #3376.
I would be inclined to stick to the initial plan and revert the other changes, or if the initial list of methods discussed are not enough to cover your use case, close the PR and invest time in shipping the feature for everyone within the boundaries of the public API.
The reason why we're reticent with making everything accessible is that we don't want to create the false expectation that all these methods/properties are there to stay.
Our commitment to avoiding breaking changes extends exclusively to public methods. Any other method or property is to be considered internal for all intents and purposes.
This is also why we're gradually moving away from private
and have started using actual JavaScript private fields (i.e. private getLogLevelNameFromNumber()
becomes #getLogLevelNameFromNumber()
).
I changed the additional methods/properties back to There is one optional comment 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.
Thank you for addressing my comments.
Looking forward to collaborating on the RFC!
|
Summary
Change the visibility of
Logger
methods fromprivate
toprotected
to allow subclassing ofLogger
to add new functionailityChanges
Issue number: #3376
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.