-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
TS definition: incorrect signatures with callback argument #1922
Comments
LogCallback is indeed not supported anymore as per version 3 and can cause confusion https://github.com/winstonjs/winston/blob/HEAD/UPGRADE-3.0.md#winstonlogger |
Ah, if this is the case, PR is welcomed here... |
@DABH FYI i just made a PR for that |
Thanks, I'll take a look... I need to think a little carefully here, because this is a breaking change, but it seems like this should not have been here in the first place... so not sure if this needs to be a major or a minor version release of winston. Feels a little funny to do a major release over some TS changes but I don't want to throw off anyone who might be using these definitions (although the thing the defs are referring to aren't supported...). @wbt any thoughts on how we semver this, if we merge it in? Open to other's opinions as well |
@DABH minor version should be okay since the functionality itself is not changing. meanwhile, as you said earlier, that the ones who are using this definitions might get shocked on their build. |
Yeah I guess I'll do that... and let you handle any complaints from users that come in ;) |
There're bunch of method signatures that contain
callback
:But actually looking at js code it doesn't seem that Winston supports any callbacks for log methods at all.
The text was updated successfully, but these errors were encountered: