bazelbuild / bazelbuild/rules_apple
Document entitlement / plist norms
- Dominant language
- Starlark
- Stars
- 593
- Forks
- 334
- Avg merge
- 16h 48m
- Merged PRs (30d)
- 9
Description
Currently when you create a new app you have to jump through some hoops to deal with default entitlements / plist replacements that Xcode handles. We should either handle them or at least document some common patterns you can use to handle them yourself
Contributor guide
Research direction
Start by reviewing how this repository currently handles entitlements and plist replacements, then compare that with the defaults Xcode applies when creating an app. The issue offers two possible outcomes—supporting the behavior or documenting common workarounds—so confirm the intended scope before starting. Done should mean the selected approach covers the common patterns clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios
- Domain
- build-system, mobile
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100