-
Notifications
You must be signed in to change notification settings - Fork 151
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
Allow to provide custom levels and custom colors #257
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.
lgtm
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.
tests must be re-enabled
@mcollina all done! Let me know if you can merge and deploy it please |
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.
Please update documentation, including the Readme.
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.
lgtm
5a14c5a
to
8d328c0
Compare
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.
Can you perform a rebase?
$ git remote add upstream https://github.com/pinojs/pino-pretty.git
$ git fetch upstream master
$ git rebase upstream/master
3186519
to
c94f89c
Compare
@jsumners I've removed |
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.
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.
lgtm
can you check CI? It was failing |
I am also very interested in this feature, so I looked into why the CI is failing. For some probably non-intentional reason in commit id c94f89c in file
instead of:
After that the tests are all green. |
Sorry if I've been AWOL, between Xmas holidays and New Year "back to work" I haven't had time to look into this issue. Thanks @dotcore for your input. The commit was made somewhat intentionally as the local test was failing and wasn't allowing me to push. I'll revert that commit and push again to see if it fixes the issue. I will also do a rebase to upstream, so we can hopefully close this PR. |
Allow to override message, greyMessage colors
c94f89c
to
871b516
Compare
@dotcore I've updated that, although my tests keep failing for the test/basic.test.js as the format is different on my machine. I'm on MacOS with node 16, which environment are you running the tests from? |
I'm on MacOS with node 17.4.0, but I also tested on node 16.13.2 and 12.22.9 (Switched with nvm). |
@dotcore for some reason this is what I see when I run
|
I can confirm that it works for me, also CI didn't fail. No idea why it does not work for you. |
Who knows 😂 |
Not sure if this may help, but maybe delete your node_modules and run |
Done |
This should provide the possibility to handle custom levels and custom colors, especially through CLI.