Skip to content

Fully qualify type names in call hierarchy, type hierarchy and workspace symbols #1844

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 3, 2024

Conversation

ahoppen
Copy link
Member

@ahoppen ahoppen commented Nov 22, 2024

Previously, we didn’t take outer types into account or only took one level of container type into account.

Fixes #1673
rdar://136078089

@ahoppen
Copy link
Member Author

ahoppen commented Nov 22, 2024

@swift-ci Please test

…ace symbols

Previously, we didn’t take outer types into account or only took one level of container type into account.

Fixes swiftlang#1673
rdar://136078089
@ahoppen ahoppen force-pushed the fully-qualified-names branch from 37034a8 to eb72e10 Compare November 22, 2024 20:33
@ahoppen
Copy link
Member Author

ahoppen commented Nov 22, 2024

@swift-ci Please test

@ahoppen
Copy link
Member Author

ahoppen commented Nov 22, 2024

@swift-ci Please test Windows

@ahoppen
Copy link
Member Author

ahoppen commented Nov 22, 2024

@swift-ci Please test Window

@ahoppen
Copy link
Member Author

ahoppen commented Dec 3, 2024

@swift-ci Please test Windows

@ahoppen ahoppen merged commit 9efa7e8 into swiftlang:main Dec 3, 2024
3 checks passed
@ahoppen ahoppen deleted the fully-qualified-names branch December 3, 2024 22:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Type hierarchy should show fully qualified type for nested types
2 participants