summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/services
diff options
context:
space:
mode:
Diffstat (limited to 'addons/web/static/src/js/services')
-rw-r--r--addons/web/static/src/js/services/notification_service.js11
1 files changed, 4 insertions, 7 deletions
diff --git a/addons/web/static/src/js/services/notification_service.js b/addons/web/static/src/js/services/notification_service.js
index a0d2720604b..ea16d9ef66f 100644
--- a/addons/web/static/src/js/services/notification_service.js
+++ b/addons/web/static/src/js/services/notification_service.js
@@ -1,9 +1,10 @@
odoo.define('web.NotificationService', function (require) {
-"use strict";
+'use strict';
var AbstractService = require('web.AbstractService');
var Notification = require('web.Notification');
var core = require('web.core');
+
var id = 0;
/**
@@ -16,9 +17,7 @@ var id = 0;
* by using this file. The proper way is to use the do_warn or do_notify
* methods on the Widget class.
*/
-
var NotificationService = AbstractService.extend({
-
custom_events: {
close: '_onCloseNotification',
},
@@ -37,8 +36,8 @@ var NotificationService = AbstractService.extend({
/**
* It may sometimes be useful to close programmatically a notification. For
- * example, when there is a sticky notification that warns the user about
- * some condition (connection lost), but the condition do not apply anymore.
+ * example, when there is a sticky notification warning the user about some
+ * condition (connection lost), but the condition does not apply anymore.
*
* @param {number} notificationId
* @param {boolean} [silent=false] if true, the notification does not call
@@ -105,9 +104,7 @@ var NotificationService = AbstractService.extend({
},
});
-
core.serviceRegistry.add('notification', NotificationService);
-
return NotificationService;
});