-
Notifications
You must be signed in to change notification settings - Fork 167
Support decoding link summaries with absolute paths to external pages #1334
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
d-ronnqvist
merged 2 commits into
swiftlang:main
from
d-ronnqvist:support-decoding-external-pages-with-absolute-urls
Nov 11, 2025
Merged
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@d-ronnqvist Could this property be made public to match the rest of this struct? It doesn't make sense to me that a client of DocC's API could access all the other properties in this structure except this one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does make sense to have API that only DocC can use but that clients can't.
In this case I'm not sure yet if this property fits into the long-term design of linking between documentation and unless we have an explicit need for making it public (in which case I would probably say we should only make it SPI) I would really prefer to not commit to its long term existence.
This type (
LinkDestinationSummary) is used for both documentation from other documentation sources (resolved via a separate process) and documentation from other DocC targets (resolved via--dependencyarguments). DocC itself doesn't produce any summaries with absolute presentation URLs but we can't make any guarantees about what other documentation systems do.At this point I would rather not have behaviors of other documentation systems impact the design for DocC's own external documentation information.