fix(adminui): OpcUaClient editor reads the legacy PascalCase NodeId at the reader's precedence (#557 item 1)

`OpcUaClientTagDefinitionFactory.TryReadNodeId` still honours a legacy PascalCase
`NodeId` when the v3 camelCase `nodeId` is wholly absent, but
`OpcUaClientTagConfigModel` read only `nodeId` — so a legacy blob was SERVED by
the driver yet opened with an empty reference field and could not be saved
untouched. Authoring stricter than the reader, which #554 names as never
legitimate: the editor was blocking config the runtime honours.

Fixed with the #550 pattern (read both spellings, normalise on save), NOT by
retiring the spelling from the reader — that would break every legacy blob the
driver currently serves at the next deploy, a data-plane regression traded for
an editor asymmetry.

The precedence is PRESENCE-shadows, not first-non-blank. The reader's
`TryGetProperty("nodeId", out n) || TryGetProperty("NodeId", out n)`
short-circuits on the mere PRESENCE of the camelCase key and then checks
string-and-non-blank ONCE, so a blank / non-string / JSON-null `nodeId` beside a
valid legacy `NodeId` is a REJECTED blob, not a fallback. Copying MTConnect's
`FirstNonBlank` walk here would have made authoring WEAKER than the reader —
the same defect in mirror image.

- `NodeIdKeys` drives both halves, so the read and the drop cannot drift.
- `ToJson` writes `nodeId` and drops `NodeId`; the TagModal history-merge keys
  (`isHistorized` / `historianTagname`) are disjoint and untouched.
- `Validate`'s required-reference fast path is now precedence-aware by
  construction, so it agrees with the #554 parse consult across the whole
  rejection surface.
- The `TagConfigNonEnumParityTests` exemption for OpcUaClient is REMOVED — its
  anti-vacuity guard `Every_deliberately_stricter_entry_is_still_exactly_that`
  went red on the fix, which is this change's falsification control. The legacy
  shapes moved into the corpus, where both fleet theories now cover them.

Tests: a nine-row precedence theory driving the authoring verdict against the
READER's verdict per shape, on the original blob AND on the `ToJson()` output;
no-retype (legacy loads showing its reference, saves canonical, same node id
before and after); no-drift (output never carries `NodeId`). Each half was
reverted in isolation to confirm it reddens tests of its own: read-only-revert
=> 6 red incl. the fleet parity theory; drop-only-revert => 4 red.

Suites: AdminUI.Tests 1459/1459, ControlPlane.Tests 261/261,
Driver.OpcUaClient.Tests 143/143, Driver.OpcUaClient.Browser.Tests 10/10.
This commit is contained in:
Joseph Doherty
2026-08-10 03:01:41 -04:00
parent ca3968cc31
commit be5899bc7d
6 changed files with 255 additions and 17 deletions
@@ -1,6 +1,7 @@
using Shouldly;
using Xunit;
using ZB.MOM.WW.OtOpcUa.AdminUI.Uns.TagEditors;
using ZB.MOM.WW.OtOpcUa.Driver.OpcUaClient;
namespace ZB.MOM.WW.OtOpcUa.AdminUI.Tests.Uns;
@@ -102,4 +103,130 @@ public sealed class OpcUaClientTagConfigModelTests
{
new OpcUaClientTagConfigModel { NodeId = "ns=2;s=X" }.Validate().ShouldBeNull();
}
// =============================================================================================
// Gitea #557 item 1 — the legacy PascalCase "NodeId" spelling.
//
// The reader (OpcUaClientTagDefinitionFactory.TryReadNodeId) still honours it when the v3 camelCase
// "nodeId" is WHOLLY ABSENT, while this model read only "nodeId" — so a legacy blob was SERVED by the
// driver yet opened with an empty field and could not be saved untouched. Authoring stricter than the
// reader, which #554 names as never legitimate. The fix is the #550 pattern applied to this reader's
// own precedence: read both spellings at the reader's exact walk, write only "nodeId", drop the legacy.
//
// ⚠️ Retiring the spelling from the READER instead was rejected: it would break every legacy blob the
// driver currently serves at the next deploy — a data-plane regression to fix an editor asymmetry.
// =============================================================================================
/// <summary>
/// ⚠️ <b>The precedence is PRESENCE-shadows, not first-non-blank</b>, and every shape below is a
/// shape those two rules disagree about. The reader's
/// <c>TryGetProperty("nodeId", out n) || TryGetProperty("NodeId", out n)</c> short-circuits on the
/// mere PRESENCE of the camelCase key and then checks string-and-non-blank ONCE — so a blank or
/// non-string <c>nodeId</c> beside a valid legacy <c>NodeId</c> is a REJECTED blob, not a fallback.
/// Had this model copied <c>MTConnectTagConfigModel</c>'s <c>FirstNonBlank</c> walk it would accept
/// those three shapes and the driver would skip the tag — the exact defect #554 forbids, introduced
/// while fixing its mirror image.
/// <para>
/// The verdict is asserted against the READER for every shape, so the expectations below cannot
/// drift from the authority they claim to mirror, and it is asserted on the <c>ToJson()</c>
/// output as well as the original — a normalisation that changed the verdict would be a
/// save that silently made a tag readable or unreadable.
/// </para>
/// </summary>
[Theory]
// 1. camelCase only — the v3 shape.
[InlineData("""{"nodeId":"ns=2;s=A"}""", true, "ns=2;s=A", "camelCase only")]
// 2. legacy only — the #557 shape: the reader serves it, so authoring must accept it.
[InlineData("""{"NodeId":"ns=2;s=A"}""", true, "ns=2;s=A", "legacy PascalCase only, camelCase wholly absent")]
// 3. both present — camelCase wins; the legacy value must never be displayed or saved.
[InlineData("""{"nodeId":"ns=2;s=New","NodeId":"ns=2;s=Old"}""", true, "ns=2;s=New", "camelCase out-ranks legacy")]
// 4. blank camelCase beside a valid legacy — SHADOWS. first-non-blank would wrongly accept this.
[InlineData("""{"nodeId":"","NodeId":"ns=2;s=Old"}""", false, "", "a present-but-blank camelCase key shadows the legacy one")]
// 5. non-string camelCase beside a valid legacy — SHADOWS, same reason.
[InlineData("""{"nodeId":5,"NodeId":"ns=2;s=Old"}""", false, "", "a present-but-non-string camelCase key shadows the legacy one")]
// 5b. JSON null is 'present' to TryGetProperty, so it shadows too — ValueKind.Null is not String.
[InlineData("""{"nodeId":null,"NodeId":"ns=2;s=Old"}""", false, "", "a present JSON-null camelCase key shadows the legacy one")]
// 6. blank legacy, no camelCase — nothing usable anywhere.
[InlineData("""{"NodeId":""}""", false, "", "a blank legacy key is no reference at all")]
[InlineData("""{"NodeId":5}""", false, "", "a non-string legacy key is no reference at all")]
// 7. neither spelling.
[InlineData("{}", false, "", "no reference under either spelling")]
public void Authoring_judges_every_spelling_shape_exactly_as_the_reader_does(
string blob, bool readerAccepts, string expectedNodeId, string why)
{
// The authority, first: if the reader's own verdict ever changes, this row fails here rather than
// quietly re-basing the parity claim onto whatever the model happens to do.
OpcUaClientTagDefinitionFactory.TryReadNodeId(blob, out var readerNodeId).ShouldBe(
readerAccepts, $"the reader's verdict for this blob is the premise of the row ({why}). Blob: {blob}");
var model = OpcUaClientTagConfigModel.FromJson(blob);
model.NodeId.ShouldBe(
expectedNodeId,
$"the editor must show the reference the DRIVER would read, not a different spelling's ({why}).");
if (readerAccepts) { model.NodeId.ShouldBe(readerNodeId); }
(model.Validate() is null).ShouldBe(
readerAccepts,
$"authoring and the reader disagree about this blob ({why}). Blob: {blob}");
// And the same verdict must survive the save: normalisation may rewrite the spelling, never the
// answer. (A refused blob is still serialisable — the operator has to be able to open and fix it.)
OpcUaClientTagDefinitionFactory.TryReadNodeId(model.ToJson(), out _).ShouldBe(
readerAccepts, $"ToJson() changed the reader's verdict ({why}). Blob: {blob}");
}
/// <summary>
/// The no-retype guarantee, which is the operator-visible half of #557: a legacy blob loads showing
/// its real reference, saves as the canonical camelCase key, and the DRIVER reads the same node id
/// before and after. Before the fix the field opened empty and a save blanked the binding.
/// </summary>
[Fact]
public void A_legacy_blob_saves_untouched_to_the_canonical_key_without_retyping_the_reference()
{
const string legacy = """{"NodeId":"nsu=urn:plc:sim;s=Line1.Speed"}""";
OpcUaClientTagDefinitionFactory.TryReadNodeId(legacy, out var before).ShouldBeTrue();
var saved = OpcUaClientTagConfigModel.FromJson(legacy).ToJson();
saved.ShouldContain("""
"nodeId":"nsu=urn:plc:sim;s=Line1.Speed"
""".Trim());
OpcUaClientTagDefinitionFactory.TryReadNodeId(saved, out var after).ShouldBeTrue(
"a save must never make a served tag unreadable.");
after.ShouldBe(before, "the save re-bound the tag to a different upstream node.");
}
/// <summary>
/// The drop half of the #550 pattern. Leaving the legacy key in the bag would let the two spellings
/// drift apart on the next edit, and would leave a key that only exists to be misread. Every save
/// path — a loaded legacy blob, a loaded both-spellings blob, a freshly authored model — emits the
/// canonical key alone.
/// </summary>
[Theory]
[InlineData("""{"NodeId":"ns=2;s=A"}""")]
[InlineData("""{"nodeId":"ns=2;s=New","NodeId":"ns=2;s=Old"}""")]
[InlineData("""{"NodeId":"ns=2;s=A","samplingIntervalMs":250}""")]
[InlineData("""{"NodeId":""}""")]
public void ToJson_never_re_emits_the_legacy_PascalCase_key(string blob)
{
var saved = OpcUaClientTagConfigModel.FromJson(blob).ToJson();
saved.ShouldNotContain("\"NodeId\"", Case.Sensitive,
"the legacy spelling must be normalised away on save, not carried alongside the canonical key.");
saved.ShouldContain("\"nodeId\":", Case.Sensitive);
}
/// <summary>An unrelated key still survives a legacy-spelled load→save — the drop is surgical.</summary>
[Fact]
public void Normalising_the_legacy_key_preserves_every_other_key()
{
var saved = OpcUaClientTagConfigModel
.FromJson("""{"NodeId":"ns=2;s=A","samplingIntervalMs":250,"isHistorized":true}""")
.ToJson();
saved.ShouldContain("\"samplingIntervalMs\":250");
saved.ShouldContain("\"isHistorized\":true");
saved.ShouldContain("\"nodeId\":\"ns=2;s=A\"");
}
}
@@ -164,6 +164,23 @@ public sealed class TagConfigAuthoringDeployParityTests
AssertParity(DriverTypeNames.OpcUaClient, model.Validate(), model.ToJson());
}
/// <summary>
/// Gitea #557 item 1 — a LEGACY PascalCase <c>NodeId</c> blob, which the reader has always served.
/// Both directions are asserted at once: the editor now accepts it as loaded (it used to refuse a
/// config the driver honours), and the blob it saves is still clean at the deploy gate. The two
/// configs differ — the second is the normalised <c>nodeId</c> rewrite — so passing this needs the
/// read half AND the drop half to agree.
/// </summary>
[Fact]
public void OpcUaClient_legacy_spelled_config_is_authorable_and_stays_clean_after_normalisation()
{
const string legacy = """{"NodeId":"nsu=urn:plc:sim;s=Line1.Speed"}""";
var model = OpcUaClientTagConfigModel.FromJson(legacy);
AssertParity(DriverTypeNames.OpcUaClient, model.Validate(), legacy);
AssertParity(DriverTypeNames.OpcUaClient, model.Validate(), model.ToJson());
}
/// <summary>
/// Falsifiability control. Every assertion above would also pass against a build where the four G-7
/// inspectors were never wired — an unmapped driver type returns no warnings for anything. This one
@@ -375,6 +375,17 @@ public sealed class TagConfigNonEnumParityTests
(DriverTypeNames.OpcUaClient, """{"nodeId":"nsu=urn:plc:sim;s=Line1.Speed"}"""),
(DriverTypeNames.OpcUaClient, """{"nodeId":""}"""),
(DriverTypeNames.OpcUaClient, """{"nodeId":5}"""),
// Gitea #557 item 1 — the legacy PascalCase spelling, in every shape the reader's PRESENCE-shadows
// precedence distinguishes. These used to live one-line in DeliberatelyStricter; the fleet theories
// now cover them, in both directions, which is what removing that exemption bought.
(DriverTypeNames.OpcUaClient, """{"NodeId":"nsu=urn:plc:sim;s=Line1.Speed"}"""),
(DriverTypeNames.OpcUaClient, """{"nodeId":"nsu=urn:plc:sim;s=New","NodeId":"nsu=urn:plc:sim;s=Old"}"""),
// ⚠️ The three that a first-non-blank walk would get WRONG: a present-but-unusable camelCase key
// SHADOWS the legacy one, so these are refusals, not fallbacks to the perfectly good "NodeId".
(DriverTypeNames.OpcUaClient, """{"nodeId":"","NodeId":"nsu=urn:plc:sim;s=Old"}"""),
(DriverTypeNames.OpcUaClient, """{"nodeId":5,"NodeId":"nsu=urn:plc:sim;s=Old"}"""),
(DriverTypeNames.OpcUaClient, """{"nodeId":null,"NodeId":"nsu=urn:plc:sim;s=Old"}"""),
(DriverTypeNames.OpcUaClient, """{"NodeId":""}"""),
];
/// <summary>
@@ -472,10 +483,11 @@ public sealed class TagConfigNonEnumParityTests
[(DriverTypeNames.Calculation, """{"scriptId":"S1","timerIntervalMs":10}""")] =
"sub-50 ms timer: deliberate editor floor, honoured verbatim by the runtime",
// The reader still falls back to a legacy PascalCase NodeId when the v3 camelCase key is absent.
// Pre-dates #554 and is left alone: re-entering the reference rewrites it to the v3 key.
[(DriverTypeNames.OpcUaClient, """{"NodeId":"nsu=urn:plc:sim;s=Line1.Speed"}""")] =
"legacy PascalCase key: the reader still honours it, this editor reads only camelCase 'nodeId'",
// Gitea #557 item 1 REMOVED the OpcUaClient legacy-PascalCase entry that sat here. It was the one
// exemption that was not a deliberate editor opinion at all — it was the editor being STRICTER
// than its reader for no reason but an under-read, so a blob the driver SERVED could not be saved
// untouched. OpcUaClientTagConfigModel now reads both spellings at the reader's exact precedence
// and normalises onto 'nodeId' on save; the legacy shapes are in the corpus above instead.
};
/// <summary>
@@ -60,6 +60,12 @@ public sealed class TagConfigValidatorTests
public void OpcUaClient_with_node_id_is_valid()
=> TagConfigValidator.Validate("OpcUaClient", """{"nodeId":"ns=2;s=Line3.Temp"}""").ShouldBeNull();
// Gitea #557 item 1: the driver's reader still honours the pre-v3 PascalCase spelling when the camelCase
// key is wholly absent, so the dispatched validator must too — it used to refuse a blob the driver serves.
[Fact]
public void OpcUaClient_with_a_legacy_PascalCase_node_id_is_valid()
=> TagConfigValidator.Validate("OpcUaClient", """{"NodeId":"ns=2;s=Line3.Temp"}""").ShouldBeNull();
// Gitea #551 item 2: S7 is the one driver whose reader REQUIRES the dataType key to be present, so a
// blob carrying only an address is one the driver skips — this used to assert it was valid.
[Fact]