ifnot

[kskog]

Usually, I try to reduce nesting by checking conditions and returning as quickly as possible. This requires inverting of if statements. To improve readability, maybe you could add an ifnot or if! statement.

instead of

if (!(ev.Device.Type == DeviceType.Gateway && ev.PropertyId == MtIdentifier.NetworkMode && ev.IsChanged))
{
  return;
}

// ...

one could write like this:

ifnot (ev.Device.Type == DeviceType.Gateway && ev.PropertyId == MtIdentifier.NetworkMode && ev.IsChanged)
{
  return;
}

// ...

[ufcpp]

see #882

[jnm2]

This is a side topic, but I find this an enjoyable way to handle examples like the one you shared. It's not always applicable, though.

if (ev is not { Device.Type: DeviceType.Gateway, PropertyId: MtIdentifier.NetworkNode, IsChanged: true })