You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When rendering the variants of a node, use the topic references from the `@AlternateRepresentation` directives to populate more variants.
There is no need to report diagnostics as they would have been reported during bundle registration.
Link resolution would have already been performed at that point.
Unresolved topic references are ignored, but all resolved references are added as variants.
If there are multiple symbols per variant, Swift-DocC-Render prefers the first one that was added, which will always be the current node's symbol.
There should be no breakage and change of behaviour for anyone not using `@AlternateRepresentation`, and the current symbol's variants will always be preferred over any other.
// Only alternate representations which were able to be resolved to a reference should be included as an alternate representation.
1863
+
// Unresolved alternate representations can be ignored, as they would have been reported during link resolution.
1864
+
guard case .resolved(.success(let alternateRepresentationReference))= alternateRepresentation.reference else{
1865
+
continue
1866
+
}
1867
+
1868
+
// Add the language representations of the alternate symbol as additional variants for the current symbol.
1869
+
// Symbols can only specify custom alternate language representations for languages that the documented symbol doesn't already have a representation for.
1870
+
// If the current symbol and its custom alternate representation share language representations, the custom language representation is ignored.
0 commit comments