I tried to use DocC to generate documentation, but apparently DocC also tried to generate documentation for the library source code.
I would like to know how to avoid this behavior.
Thank you.
I tried to use DocC to generate documentation, but apparently DocC also tried to generate documentation for the library source code.
I would like to know how to avoid this behavior.
Thank you.
DocC will generate documentation for all the Swift frameworks and libraries that are part of the scheme—either directly or as a dependency of another target—that you are building, including external dependencies for which you have the source code (such as SwiftPM checkouts or CocoaPods). Please submit feedback with a description of your use case on the Feedback Assistant website.
Thank you for your reply.
For instance, I guess I can make new target for DocC as a workaround, but it's not that easy.
I'll send you a feedback as feature request.
Here is my radar FB9158224. Please take a look. Thanks.
DocC will generate documentation for all the Swift frameworks and libraries that are part of the scheme—either directly or as a dependency of another target—that you are building, including external dependencies for which you have the source code (such as SwiftPM checkouts or CocoaPods). Please submit feedback with a description of your use case on the Feedback Assistant website.
Thank you for your reply.
For instance, I guess I can make new target for DocC as a workaround, but it's not that easy.
I'll send you a feedback as feature request.
Here is my radar FB9158224. Please take a look. Thanks.