Deprecate the changeLevelName option and alias it to levelKey
#772
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
ornotandrew
commented
Feb 13, 2020
ornotandrew
commented
Feb 13, 2020
|
@jsumners deprecation warnings from other modules won't use the logger, however instead of As an off-thread aside, maybe a module (or even a pino option) for wrapping emitWarning into logger.warn would be good. |
|
So in version 7, this aliasing code will need to be removed. Do you guys have a way of tracking that in Github? Should I leave a TODO in the code? |
|
I created a project -- https://github.com/pinojs/pino/projects/2 |
This was referenced Mar 22, 2020
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 some discussion in pino-pretty about this.
I'm not sure what sort of approach is normally used when deprecating something, but I thought I'd open a PR just to get the ball rolling.