Re: [PATCH proxmox-widget-toolkit v7 21/41] notifications: matcher: add support for match expressions

["Lukas Wagner" <l.wagner@proxmox.com>]

I'll keep my reply short, I've already drafted a longer reponse but then
my mail client crashed...

On Tue Nov 3, 2026 at 1:57 PM CET, Dominik Csapak wrote:
> hi, looks mostly good to me, a few nits and comments inline
>
> no blockers for me though
> (maybe only consider them as follow up improvements or if
> you need to send another version)

I've checked with Thomas, since nothing you mentioned should affect
funtionality, I'd do these style fixes as a followup. The series is
quite huge and I'm already building another series on top of it, so
it's simpler to apply this version (unless anything else more urgent
pops up) and then go back to improve the style where you requested
changes.

>
> In general i'm not a fan of the viewmodel to be declared and modified
> in one component and the effects only applied in another
> (e.g. which match field is shown)
>
> Nothing tragic (and i think it's pre-existing),
> but the connection between components is often lost when one
> does not know what to look for....
>
> On 11/3/26 11:57 AM, Lukas Wagner wrote:
>> This patches changes to 'matcher edit window' to support the new
>> 'expression' paramter in the matcher config. Instead of of flat
>> 'match-*' configuration keys, 'expression' contains the match rules as a
>> serialized JSON blob. This allows us to create arbitrarily nested match
>> formulas.
>> 
>> Support for match expressions has to be enabled via a feature flag. This
>> avoids awkward versioned breaks between the widget toolkit package and
>> the main product.
>> 
>> The entire match rule panel has changed so much that copying the old
>> component and using that as a base was deemed more useful than modifying
>> the existing panel in-place. The old component can be removed once we
>> @@ -1013,7 +1016,7 @@ Ext.define('Proxmox.panel.MatchCalendarSettings', {
>>       initComponent: function () {
>>           let me = this;
>>           Ext.apply(me.viewModel, {
>> -            parent: me.up('pmxNotificationMatchRulesEditPanel').getViewModel(),
>> +            parent: me.up(Proxmox.Schema.notificationMatcherPanelType()).getViewModel(),
>>           });
>>           me.callParent();
>>       },
>> @@ -1091,7 +1094,7 @@ Ext.define('Proxmox.panel.MatchSeveritySettings', {
>>       initComponent: function () {
>>           let me = this;
>>           Ext.apply(me.viewModel, {
>> -            parent: me.up('pmxNotificationMatchRulesEditPanel').getViewModel(),
>> +            parent: me.up(Proxmox.Schema.notificationMatcherPanelType()).getViewModel(),
>>           });
>>           me.callParent();
>>       },
>> @@ -1164,7 +1167,7 @@ Ext.define('Proxmox.panel.MatchFieldSettings', {
>>                               regexVal += `(${currentData.value.join('|')})`;
>>                           }
>>                           regexVal += '$';
>> -                        newValue.push(regexVal);
>> +                        newValue = regexVal;
>
> doesn't that change the type from array to string now?
> does that have any obvious effects on the older code?

This change fixed a minor bug when switching from 'exact' to 'regex'
mode, it only surfaced with the new UI changes, hence I did not put it
in a separate commit. 

I don't remember the exact details about the bug, but I've reverified
that everything works as expected now, with both the old and new UI
enabled.

>
>>                       }
>>   
>>                       record.set({
>> @@ -1282,7 +1285,7 @@ Ext.define('Proxmox.panel.MatchFieldSettings', {
>>           });
>>   
>>           Ext.apply(me.viewModel, {
>> -            parent: me.up('pmxNotificationMatchRulesEditPanel').getViewModel(),
>> +            parent: me.up(Proxmox.Schema.notificationMatcherPanelType()).getViewModel(),
>>           });
>>           Ext.apply(me, {
>>               items: [