Skip to content

Show declarations when suggesting what disambiguation to add to symbol links #397

@d-ronnqvist

Description

@d-ronnqvist

Description

Currently the error messages from the path hierarchy based link resolver for when a path is ambiguous list the possible collisions and their names. However, the collision is based on the name, so all suggestions show the same name.

For example, in the "MixedLanguageFrameworkWithLanguageRefinements" test content, the path "CollisionsWithDifferentFunctionArguments/something(argument:)" will result in an error message like:

Reference is ambiguous after '/MixedFramework/CollisionsWithDifferentFunctionArguments': Add '1cyvp' to refer to 'something(argument:)'. Add '2vke2' to refer to 'something(argument:)'.

(Note that the two suggestions have the same name)

To make it possible to distinguish the collisions and know which disambiguation to add we should display the declarations instead of just the name.

rdar://100436859

Metadata

Metadata

Assignees

Labels

enhancementImprovements or enhancements to existing functionalitylink resolutionAbout DocC's link resolution system

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions