notification matcher: fix inverted match modes
The 'not' prefix is already stripped in the set() method of the view model's 'rootMode' and not present anymore when updating the store. The information about whether the mode is inverted or not is present in the 'invert' data member. Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
This commit is contained in:
parent
49f7549b75
commit
edd98f946b
@ -778,12 +778,8 @@ Ext.define('Proxmox.panel.NotificationMatchRuleTree', {
|
||||
matchCalendarStmts.push(data.value);
|
||||
break;
|
||||
case 'mode':
|
||||
if (data.value.startsWith('not')) {
|
||||
modeStmt = data.value.substring(3); // after 'not''
|
||||
invertMatchStmt = true;
|
||||
} else {
|
||||
modeStmt = data.value;
|
||||
}
|
||||
modeStmt = data.value;
|
||||
invertMatchStmt = data.invert;
|
||||
break;
|
||||
}
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user