We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I use node-notifier in windows10, but NotificationCallback output metadata puzzle me。This is my code: const notify = ({title, message}, cb) => { notifier.notify( { title: title || "Unknown title", message: message || "Unknown message", sound: true, actions: ['OK', 'Cancel'], reply: true, }, (err, response, metadata) => { console.log(metadata); cb(metadata); }); }; =====================output { "action": "buttonClicked", "notificationId": "14096", "pipe": "\\.\pipe\notifierPipe-fa8bbb26-b562-4ad7-83b6-428f77bbaaa8", "button": "OK", "version": "0.7.0", "activationType": "OK" } why not NotificationMetadata format interface NotificationMetadata { activationType?: string | undefined; activationAt?: string | undefined; deliveredAt?: string | undefined; activationValue?: string | undefined; activationValueIndex?: string | undefined; }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I use node-notifier in windows10, but NotificationCallback output metadata puzzle me。This is my code:
const notify = ({title, message}, cb) => {
notifier.notify(
{
title: title || "Unknown title",
message: message || "Unknown message",
sound: true,
actions: ['OK', 'Cancel'],
reply: true,
},
(err, response, metadata) => {
console.log(metadata);
cb(metadata);
});
};
=====================output
{
"action": "buttonClicked",
"notificationId": "14096",
"pipe": "\\.\pipe\notifierPipe-fa8bbb26-b562-4ad7-83b6-428f77bbaaa8",
"button": "OK",
"version": "0.7.0",
"activationType": "OK"
}
why not NotificationMetadata format
interface NotificationMetadata {
activationType?: string | undefined;
activationAt?: string | undefined;
deliveredAt?: string | undefined;
activationValue?: string | undefined;
activationValueIndex?: string | undefined;
}
The text was updated successfully, but these errors were encountered: