-
Notifications
You must be signed in to change notification settings - Fork 53
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
feat(attach): allow custom logger for attach neovim proc #138
Merged
Conversation
This file contains 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
rhysd
requested changes
Jan 8, 2020
rhysd
requested changes
Jan 8, 2020
rhysd
approved these changes
Jan 8, 2020
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.
Looks good to me.
@billyvg Would you also check this PR and make a new release if you're ok? |
billyvg
approved these changes
Jan 8, 2020
@kwonoj I merged. Thank you for adding this. |
justinmk
added a commit
that referenced
this pull request
Mar 18, 2024
Problem: d9bc2ef #138 allows clients to supply a custom logger, but the logger is not always used. And the winstonLogger is always initialized, even when a custom logger is given. Solution: - Update all logging calls to use the custom logger. - Skip initialization of winstonLogger if a custom logger is given.
justinmk
added a commit
that referenced
this pull request
Mar 18, 2024
Problem: d9bc2ef #138 allows clients to supply a custom logger, but the logger is not always used. And the winstonLogger is always initialized, even when a custom logger is given. Solution: - Update all logging calls to use the custom logger. - Skip initialization of winstonLogger if a custom logger is given.
justinmk
added a commit
that referenced
this pull request
Mar 18, 2024
Problem: d9bc2ef #138 allows clients to supply a custom logger, but the logger is not always used. And the winstonLogger is always initialized, even when a custom logger is given. Solution: - Update all logging calls to use the custom logger. - Skip initialization of winstonLogger if a custom logger is given.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
relates to vscode-neovim/vscode-neovim#134
current logger only allows customizable behavior via env variable which works for majority of node.js entrypoint, but some cases (like vs code extension) overriding env variable is not very much feasible cases.
NeovimClient
ctor already accepts custom logger, butattach
does not exposes it - this PR expands signature toattach
to allow specify options for customizing points.Instead of expanding param to directly accepts
logger
, it acceptsoptions
object instead for possible future customizations.