TAG001: unknown-udt-type
typeId does not name a UDT definition, or UDT inheritance is cyclic
| Code | TAG001 |
| Name | unknown-udt-type |
| Category | Tags and gateway (TAG) |
| Default severity | error |
| Enabled by default | yes |
| Fix available | no |
| ign-lint equivalent | none |
What it does
Section titled “What it does”Checks the typeId of every UDT instance (and the parent typeId of
every UDT definition) against the UDT definitions of the tag provider, and
reports UDT definitions whose parent chain leads back to themselves.
Providers whose definitions are not in the workspace are not checked.
Why is this bad?
Section titled “Why is this bad?”An instance of a missing UDT has no members: the gateway shows it with a configuration error and every binding to its members fails. An inheritance cycle makes every definition in the cycle unusable.
Example
Section titled “Example”{"name": "Motor1", "tagType": "UdtInstance", "typeId": "Motors/Motr"}Use instead:
{"name": "Motor1", "tagType": "UdtInstance", "typeId": "Motors/Motor"}Generated from the rule metadata by iglint generate-docs; iglint rule TAG001 prints the same page in the terminal. Source: docs/rules/TAG001.md.