MobileNativeFoundation / MobileNativeFoundation/rules_xcodeproj
Feature Request: Xcode project lock file
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 626
- Forks
- 124
- PR merge metrics
- No merged PRs in 30d
Description
Consider some lockfile-like mechanism which can ensure to some degree when the project needs to be regenerated.
There are times when the project needs to be re-generated, to get BUILD file changes, target changes, etc. It would be good to have the build fail with some warning when this is detected to be required.
This will better surface errors that would be fixed by a regeneration.
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
Start by reviewing how rules_xcodeproj generates Xcode projects and detects changes to BUILD files, targets, and other project inputs. Determine what regeneration state a lock file would record and how the build could warn when that state is outdated. Done means the behavior and lock-file format are specified, implemented, and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100