-
Notifications
You must be signed in to change notification settings - Fork 322
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
Automagically Bind notify
Methods
#306
Conversation
Automagically bind `notify` methods on all wrapper classes so the notify method can be destructured within the import statement and not run into any `this` related errors.
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.
Oh! Missed this one! Thanks for submitting it. I get this can be frustrating when doing destructuring for instance. I think it looks fine. Could you remove package-lock.json from the commit also?
Revert the changes made to `package-lock.json` in the commit 789c544.
Thanks! |
How is this breaking? 🤔 |
Strictly not very breaking. The most notable breaking I found was sanitizing timeout on snoretoast handling (see changelog https://github.com/mikaelbr/node-notifier/blob/master/CHANGELOG.md#breaking-changes). But I also marked this as breaking in the changelog as it, in theory, does break from existing API. |
Thanks |
Automagically bind
notify
methods on all wrapper classes so the notify method can be destructured within the import statement and not run into anythis
related errors.