fix(drivers): align probe DriverType strings with AdminUI keys

ModbusDriverProbe.DriverType was "Modbus" but the AdminUI's
ModbusDriverPage persists DriverInstance.DriverType = "ModbusTcp".
GalaxyDriverProbe used the runtime DriverTypeName constant
("GalaxyMxGateway") but the AdminUI saves "Galaxy". The probe DI
lookup is case-insensitive but not name-insensitive, so Test
Connect would fail to find a probe for these two drivers.
This commit is contained in:
Joseph Doherty
2026-05-28 10:55:15 -04:00
parent c19d124e89
commit 54f0dbddb9
2 changed files with 3 additions and 2 deletions
@@ -24,7 +24,8 @@ public sealed class GalaxyDriverProbe : IDriverProbe
};
/// <inheritdoc />
public string DriverType => GalaxyDriverFactoryExtensions.DriverTypeName; // "GalaxyMxGateway"
// Matches DriverInstance.DriverType strings set by the AdminUI's GalaxyDriverPage.
public string DriverType => "Galaxy";
/// <inheritdoc />
public async Task<DriverProbeResult> ProbeAsync(string configJson, TimeSpan timeout, CancellationToken ct)
@@ -22,7 +22,7 @@ public sealed class ModbusDriverProbe : IDriverProbe
};
/// <inheritdoc />
public string DriverType => "Modbus";
public string DriverType => "ModbusTcp";
/// <inheritdoc />
public async Task<DriverProbeResult> ProbeAsync(string configJson, TimeSpan timeout, CancellationToken ct)