[5.7] use default branches for unknown symbol kinds
#133
Conversation
This file contains hidden or 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
|
@swift-ci Please test |
|
@swift-ci Please test Linux |
franklinsch
approved these changes
Apr 12, 2022
|
@swift-ci Please test Linux |
|
@swift-ci Please test |
QuietMisdreavus
force-pushed
the
5.7/case-default
branch
from
ffad803 to
c40c26e
Compare
|
@swift-ci Please test |
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.
This is a cherry-pick of #132 onto
release/5.7.Explanation: In preparation for updating the way symbol kinds are stored in the symbol graph, this PR changes the way swift-docc matches on that type to use a
defaultbranch instead of an explicitcase .unknown.Scope: No effect on user experience.
Radar: None, though this is a prerequisite for landing rdar://84276085
Risk: Low. This should offer no change to the behavior or test outcomes of Swift-DocC.
Testing: Ensure that the behavior of Swift-DocC does not change compared to beforehand.