-
Notifications
You must be signed in to change notification settings - Fork 152
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
Discrepancy in TypeScript types #273
Comments
Thanks for reporting! |
tearwyx
added a commit
to tearwyx/pino-pretty
that referenced
this issue
Nov 21, 2021
tearwyx
added a commit
to tearwyx/pino-pretty
that referenced
this issue
Nov 21, 2021
tearwyx
added a commit
to tearwyx/pino-pretty
that referenced
this issue
Nov 21, 2021
tearwyx
added a commit
to tearwyx/pino-pretty
that referenced
this issue
Nov 21, 2021
tearwyx
added a commit
to tearwyx/pino-pretty
that referenced
this issue
Nov 21, 2021
kibertoad
pushed a commit
that referenced
this issue
Nov 22, 2021
Having the same issue with the type Prettifier
|
@SushiWaUmai Can you send a PR with tests? |
If it is the same issue, there is no need to fix it once it has been fixed in the main branch (#274) and hopefully it will get out someday. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
According to the module
pino-abstract-transport
the function exported by default returns a value of typeTransform
from the modulestream
, but in the declaration file it returns type(inputData: string | object) => string
.Based on version 7.2.0.
The text was updated successfully, but these errors were encountered: