Update documentation script to remove symlink and use podfile for module spec #416
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
julianlocke
force-pushed
the
documentation-generation-changes
branch
from
712bdf6
to
f4ed3b4
Compare
|
LGTM |
jaquish
approved these changes
Apr 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are two changes here caused by two limitations:
Sourcekitten is attempting to look up relevant module in
.build/debug.yamlunder "commands" using the "module-name" key which no longer is included in that node. This causes jazzy generation to fail withCould not find SPM module 'SwiftyDropbox'. Here are the modules available:[]. The temporary fix here is to use the pod spec based module specification which still works.gh-pages no longer supports symlinks. Our old paradigm here was to create a folder of documentation for each version of the SDK and then symlink it to latest. Our README and most historical shared links to documentation used URLs built off of
latest. Since symlinks are no longer supported, we now need to copy the contents over instead.