Add optionalMemberOf symbol under the correct container symbol
#760
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rdar://119183922
|
@swift-ci please test |
franklinsch
approved these changes
Dec 5, 2023
d-ronnqvist
added a commit
to d-ronnqvist/swift-docc
that referenced
this pull request
Dec 7, 2023
d-ronnqvist
added a commit
to d-ronnqvist/swift-docc
that referenced
this pull request
Dec 7, 2023
d-ronnqvist
added a commit
to d-ronnqvist/swift-docc
that referenced
this pull request
Dec 7, 2023
d-ronnqvist
added a commit
that referenced
this pull request
Dec 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug/issue #, if applicable: rdar://119183922
Summary
Fix a bug where
optionalMemberOfrelationships weren't considered when building the path hierarchy, resulting in incorrect behavior if more than one symbol exist with the container's name.Dependencies
None
Testing
Describe how a reviewer can test the functionality of your PR. Provide test content to test with if
applicable.
Steps:
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.
./bin/testscript and it succeeded[ ] Updated documentation if necessary