-
-
Notifications
You must be signed in to change notification settings - Fork 616
Inherit methodFactory
extensions from the parent to the child loggers.
#4809
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
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
4d7ab1c
use methodFactory extensions from the rootLogger in child loggers.
toger5 3a80fc8
use simple method factory copy AND `childLogger.setLevel(childLogger.…
toger5 7a025e4
add comments and find a way to make it clearer that the types are co…
toger5 b9a0660
review
toger5 361c636
additionally fix MatrixRTCSessionManager being initialized before the…
toger5 ec385ec
Add comment to clarify order of log extensions and creating childs.
toger5 54ecd1f
review
toger5 4131970
Set "loglevel" min version to guarantee access to `logger.rebuild`
toger5 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
FTR, I think this could equally be
^1.9.0
, since that's where.rebuild
was introduced, but I don't imagine it makes much difference in practice.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.
It does not hurt to include the minor patches.
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.
In this specific situation, I agree, but in general, that's not correct.
The reason it might hurt is that a downstream application may have specifically decided that they want to use 1.9.0 or 1.9.1, for some reason and pinned their dependencies accordingly. (For example, maybe it turns out that 1.9.2 introduces a regression in their application). There is no need for matrix-js-sdk to insist on 1.9.2, and as a general principle
package.json
should list the earliest versions that we are compatible with.Nevertheless that seems an unlikely scenario here. So I'm not going to insist you change it. But bear in mind for future :).