Skip to content

Spike: surface SwiftPM repository guidance in Xcode - #7647

Draft
ajpallares wants to merge 8 commits into
mainfrom
codex/warn-full-spm-repository
Draft

Spike: surface SwiftPM repository guidance in Xcode#7647
ajpallares wants to merge 8 commits into
mainfrom
codex/warn-full-spm-repository

Conversation

@ajpallares

@ajpallares ajpallares commented Sep 7, 2026

Copy link
Copy Markdown
Member

Checklist

  • If applicable, unit tests
  • If applicable, create follow-up issues for purchases-android and hybrids

Motivation

Developers can unknowingly add the full source repository through SwiftPM and incur much slower download and dependency-resolution times. Point them to the optimized mirror when that happens.

Description

Use a compile-time #warning in Package.swift because Xcode preserves manifest compiler diagnostics but suppresses successful manifest runtime output.

Known limitation: purchases-ios-spm release tags are byte-identical to purchases-ios tags, so the optimized mirror and local development checkouts receive the same warning. Package.swift has no repository-identity conditional compilation value, so scoping this warning requires changing the mirror publication model.

Verified in Xcode package resolution with the Sample project, with swift package manifest evaluation, and with SwiftLint.

@ajpallares ajpallares changed the title Warn when SwiftPM uses the full source repository Spike: surface SwiftPM repository guidance in Xcode Sep 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant