yonaskolb / yonaskolb/XcodeGen
Don't overwrite shared schemes
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 8.8k
- Forks
- 908
- Avg merge
- 17d 14h
- Merged PRs (30d)
- 2
Description
Currently if you define schemes in your project configuration, they will be created as shared schemes. This also overwrites any existing shared schemes. The problem is that if you create a scheme in the Xcode UI, it defaults to share so if a user forgets to uncheck that when creating a custom scheme, their schemes will be overwritten the next time they generate.
I think ideally any shared schemes in XcodeGen would just be added along side any currently existing shared schemes (unless they have the same name, at which point they should be overwritten)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a file or test. Start by tracing how project configuration creates shared schemes, then check the generated project against existing shared schemes. Done means existing schemes remain unless an XcodeGen scheme has the same name, in which case it is replaced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100