yonaskolb / yonaskolb/XcodeGen
Wrong settings generated when using configs with the same name pattern
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 8.8k
- Forks
- 908
- Avg merge
- 17d 14h
- Merged PRs (30d)
- 2
Description
I'm facing a problem with the generated configurations when I'm using snake case. For example if I use production and production_china as configs and have settings set to them. Both generated settings will follow production instead of their respective config.
Problem:
Config
Setting
Generated Xcode Setting - Notice the values
Workaround: Change cases
Config
Setting
Generated Xcode Setting
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
Reproduce the issue with production and production_china configurations, then inspect the generated Xcode settings and the configuration-matching path. Done means each configuration produces settings using its own values rather than matching the shorter shared name.
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
- 35/100