Why is SwiftDocCPlugin included by default? #1952
-
What is the benefit for me who wants to use Kingfisher only? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
Ummm, this is for generating the DocC documentation here. Indeed it is not a necessary for framework users, but it has to be existing as a dependency of the package to allow Swift Index to build the doc and continue the following process. Unfortunately, Xcode will just also fetch it and show in the dependencies tree. But the good news is this plugin package is not added to your runtime at all and there is a system-wide cache so you only download it once. @daveverwer, Not sure if it is a good way to mention you here, but do you have any comment on this? Is there a recommended way for users to not containing the DocC plugin in their project? I am now following your instruction to add the plugin like this: #if swift(>=5.6)
// Add the documentation compiler plugin if possible
package.dependencies.append(
.package(url: "https://github.com/apple/swift-docc-plugin", from: "1.0.0")
)
#endif Maybe there is a chance to have some additional compilation flag or environment values to refine the dependency better for framework user? |
Beta Was this translation helpful? Give feedback.
Ummm, this is for generating the DocC documentation here.
Indeed it is not a necessary for framework users, but it has to be existing as a dependency of the package to allow Swift Index to build the doc and continue the following process. Unfortunately, Xcode will just also fetch it and show in the dependencies tree. But the good news is this plugin package is not added to your runtime at all and there is a system-wide cache so you only download it once.
@daveverwer, Not sure if it is a good way to mention you here, but do you have any comment on this? Is there a recommended way for users to not containing the DocC plugin in their project? I am now following your instruction to add the pl…