In Xcode 16 / Swift 6, a lot of SwiftUI view extensions we have documentation for "moved" from the SwiftUI module to some module called SwiftUICore. It sounds like a detail of how SwiftUI modularizes internally is leaking out via DocC. Is this a bug that should be reported? Is it how DocC is intended to work and should we migrate our documentation to reference this "core" module instead?
4 Likes
I am not sure what you mean exactly, but in general if it's an Xcode/Apple specific problem, it's best to raise a feedback in the "Developer Tools & Resources" section.
It's not Xcode-specific. Here's an example hosted DocC page that shows the problem:
https://swiftpackageindex.com/pointfreeco/swift-navigation/main/documentation/swiftnavigation
Note that there are 2 extended modules, SwiftUI and SwiftUICore. This leads me to believe that the SwiftUI team has begun to internally modularize and re-export those modules from SwiftUI, but that detail is leaking out via DocC. Apple's own documentation doesn't mention SwiftUICore, so it's not clear to me how a person documenting a library that extends SwiftUI should know which internal SwiftUI module to reference depending on the API.
3 Likes
This should be resolved in the latest swift nightly toolchains, if it isn't please let us know.
1 Like