You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should avoid using hardcoded absolute link in Documentation bundle.
The result is the web version is fine but build and open the documentation in Xcode will give us a bad navigation experience - Opening a new web tab instead of navigating the corresponding page.
Also it will increase the cost when we want to deploy our documentation in other platform other than GitHub page. (eg. SwiftPackageIndex)
The text was updated successfully, but these errors were encountered:
Are you referring to the links between the packages? I couldn't figure out any other way to get them -- it looks like the cross package links are still in the future.
We could potentially switch them to relative links. That would fix the hosting issue I think, but not viewing in Xcode docs.
Are you referring to the links between the packages? I couldn't figure out any other way to get them -- it looks like the cross package links are still in the future.
Got it. I'm tracking this on the swift-docc side. It is indeed not supported currently on the upstream.
We should avoid using hardcoded absolute link in Documentation bundle.
The result is the web version is fine but build and open the documentation in Xcode will give us a bad navigation experience - Opening a new web tab instead of navigating the corresponding page.
Also it will increase the cost when we want to deploy our documentation in other platform other than GitHub page. (eg. SwiftPackageIndex)
The text was updated successfully, but these errors were encountered: