yonaskolb / yonaskolb/XcodeGen
Local packages with custom group not showing in generated project
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 8.8k
- Forks
- 908
- Avg merge
- 17d 14h
- Merged PRs (30d)
- 2
Description
#1175 added the ability to specify a custom group but to me it's not behaving like I would expect it to.
I would expect it to create the group structure i specify, for example:
packages:
AlamofireNetworkClient:
path: Packages/AlamofireNetworkClient
AppEnvironment:
path: Packages/Group2/AppEnvironment
group: Packages/Group2
...
This should result in the following structure in Xcode
Project
- Packages
- AlamofireNetworkClient
- Group2
- AppEnvironment
Instead, the Group2 and it's content is simply not showing up in the generated project at all.
It will only work if the whole group chain already exists through other means.
The same issue was previously described in #1118.
#1392 also seems to ask about the possibility of doing this.
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 file or test is named in the issue; start by reproducing the YAML package configuration and tracing the generated Xcode project structure for a missing parent group. Done means a package whose custom group path does not already exist appears under the requested nested groups, while existing package behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100