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
[SR-15431] Support DocC references to symbols defined in another module #208
Comments
|
This has also been filed in Feedback Assistant with FB9410972 |
|
Comment by Ellen Shapiro (JIRA) This would also be super-helpful for us at Apollo GraphQL - we have small sub-libraries for things like handling a SQLite persistence layer and WebSockets that we would love to be able to link to our main lib as well. |
|
Comment by Alexey Ivashko (JIRA) +1 on this. I distribute internal frameworks as one package but as several different libraries in order to use only the code I needed for my targets. Referencing another module from my own would be such a pleasure, because I have several "protocol" only frameworks that have "concrete" frameworks implementations. And also, sometimes I would like to reference existing system framework documentation in order to guide user to fully learn about my api |
|
Comment by Martin Heinrich (JIRA) +1 for this request |
|
+1 on this as well. We'd also need to cross-reference across targets in the Distributed Tracing repos. |
|
Comment by Akos Polster (JIRA) |
|
any news for this ? |
Additional Detail from JIRA
md5: c3c52c8ed342d1b0fea2c443bcf8f543
Issue Description:
As a database driver author, I rely heavily on SwiftNIO for the architecture of my driver, and users of my driver should be familiar with many of the concepts and types defined by SwiftNIO that I also expose.
When I write symbol documentation or articles, I would like the ability to reference those types, to enrich the exploration of documentation with Xcode.
The syntax I would find the least surprising is having to prepend the module's name at the start, such as
``SlothCreator/Habitat``The text was updated successfully, but these errors were encountered: