[iOS][swiftpm] Documentation updates - #58084
Open
chrfalch wants to merge 1 commit into
Open
Conversation
The derivation rule, the `spm.name` override and the names React Native reserves were only discoverable from the autolinker's source or from the error a collision produces. Write them down where a library author looks: the scoped package case that surprises people (`@scope/react-native` derives `ReactNative`, and gets its scope back as `ScopeReactNative`), the two reasons to set `spm.name` and its charset, the reserved names in one table, what happens when two libraries derive the same name — who moves, who stays, and when the build fails anyway — and the npm `files` requirement that makes the override reach consumers at all. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Caution Invalid Base Branch The base branch for this PR is |
This file contains hidden or 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
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.
Summary:
There were some missing explanation regarding naming of SwiftPM modules which led to some issues for library authors, and based on changes in the functionality the docs also needed a few minor updates to support these changes (we're still in preview, so changes are expected).
This PR updates the docs.
Changelog:
[IOS] [FIXED] - Updated SwiftPM documentation
Test Plan:
✅ Verify that the docs are aligned with the implementation