dohertj2/lmxopcua
1
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases Wiki Activity

docs(mtconnect): state the driverDataType-over-dataType precedence and the editor's normalisation (#550)

Browse Source
This commit is contained in:
Joseph Doherty
2026-08-09 23:48:09 -04:00
parent 8971861b7c
commit a486a009dc
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/drivers/MTConnect.md
+7 -1
View File
@@ -180,7 +180,13 @@ into) is resolved in this order, first non-null wins:
1. The `RawTags[]` blob's `driverDataType` or `dataType` field (both 1. The `RawTags[]` blob's `driverDataType` or `dataType` field (both
spellings accepted — the typed editor writes `dataType`, the driver's own spellings accepted — the typed editor writes `dataType`, the driver's own
`tags[]` shape uses `driverDataType`). `tags[]` shape uses `driverDataType`). **`driverDataType` wins when it is
non-blank**, and a present-but-invalid one rejects the tag rather than
falling through to `dataType`. The AdminUI's typed editor mirrors that
precedence on load and **normalises onto `dataType`, dropping the alias, on
save** (Gitea #550) — so a tag edited through the editor keeps the type the
driver read for it, and an unreadable spelling is refused at authoring
instead of dying at the driver.
2. A matching `Tags[]` entry naming the same DataItem id. 2. A matching `Tags[]` entry naming the same DataItem id.
3. The Agent's own `/probe` declaration, via `MTConnectDataTypeInference.Infer` 3. The Agent's own `/probe` declaration, via `MTConnectDataTypeInference.Infer`
(category/type/units/representation → `DriverDataType`). (category/type/units/representation → `DriverDataType`).