NIM0003: Ambiguous help link
NIM0003 reports an ambiguous link in the generated driver help — a cross-reference whose name matches more than one driver item. Nimbus cannot determine which was intended, so it leaves the link unresolved rather than choosing one silently.
This is distinct from NIM0001, which reports a link that matches nothing. The two carry different remedies: a broken link is corrected or its target created, while an ambiguous link is narrowed.
Common causes
Section titled “Common causes”- A link written as a bare name, such as
xref:Configure, where the driver declares that member on several types. - A link to an overloaded method, where the name alone does not identify one overload.
- A link to a generic method, where the name alone does not identify one arity.
How to fix it
Section titled “How to fix it”The diagnostic message lists the items that share the name and states which of the two remedies below applies. A name shared by many items shows a sample of them rather than the whole set.
When the items are overloads
Section titled “When the items are overloads”Add a qualifier. Neither qualifier character can appear in an identifier, so a name is never mistaken for one:
| Form | Selects |
|---|---|
xref:Configure-2 | The overload taking two parameters. |
xref:Transform`1 | The generic overload with one type parameter. |
xref:Transform`2-6 | One type parameter count and one parameter count together. |
When the items differ only by declaring type
Section titled “When the items differ only by declaring type”A qualifier cannot help here: the items have the same parameter count and the same generic arity, so no combination of the two separates them. Name the declaring type instead:
[Configure](xref:Acme4301ArmSource.Configure)The namespace-qualified form resolves as well, and is needed only where two types in different namespaces share a short name:
[Configure](xref:Acme.Acme4301.Acme4301ArmSource.Configure)The message prints whichever form distinguishes the candidates — the short one unless short names collide — so a candidate can be copied directly into a link.
Alternatively, use the Copy Help Link command in the Driver Designer and paste the result. That produces a link keyed on the item’s identity rather than its name, which is never ambiguous and survives a rename. See Using the Help Editor.
Configuring this diagnostic
Section titled “Configuring this diagnostic”Set the NIM0003Severity property to control how this diagnostic is treated (None,
Information, Warning, or Error). It defaults to Error in Release builds and Warning
otherwise. See Configuring Driver Design Analysis.