MobileNativeFoundation / MobileNativeFoundation/rules_xcodeproj
Bug: When target consolidation fails, there is no way to create custom schemes that build the various splits
Open
Nobody has claimed this yet.
bug
- Dominant language
- Swift
- Stars
- 626
- Forks
- 124
- PR merge metrics
- No merged PRs in 30d
Description
Description
https://bazelbuild.slack.com/archives/C0429BN0F8V/p1681135386611619
rules_xcodeproj version
1.3.3
Xcode version
Any
Bazel version
Any
rules_apple version
No response
rules_swift version
No response
Additional information
No response
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
No source file, test, or entry point is named. Start with the linked Slack discussion and the target-consolidation/custom-scheme implementation in rules_xcodeproj; done means providing a way to define custom schemes that build the relevant splits when consolidation fails, with coverage for that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100