Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move playground to its own repo #1866

Closed
hwillson opened this issue Jul 8, 2021 · 0 comments · Fixed by #1905
Closed

Move playground to its own repo #1866

hwillson opened this issue Jul 8, 2021 · 0 comments · Fixed by #1905
Assignees

Comments

@hwillson
Copy link
Member

hwillson commented Jul 8, 2021

We want to move the Playground with examples of how to set things up for Apollo-iOS to its own repo for a couple of reasons:

  • Discoverability: Most people have no idea it exists. Having its own repo will help with visibility
  • Decoupling: This will help decouple changes to the repo vs. changes to the playground. This will allow us to update the playground when a new version is released more easily, and not have a mix of released and unreleased changes in the playground.
  • Carthage: Carthage automatically builds every shared scheme in a given xcodeproj in the root of a repo. There is not a way within Carthage to exclude or include specific schemes. This is a real pain for the playground scheme since it builds all sub-libraries, and vastly bloats Carthage build time for our library.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants