yonaskolb / yonaskolb/XcodeGen
What is the expected copy behavior for Swift playgrounds?
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 8.8k
- Forks
- 908
- Avg merge
- 17d 14h
- Merged PRs (30d)
- 2
Description
There has been some discussion in #894 about the expected copy behavior of a Swift playground. In v2.15.1, a Swift playground is apparently copied as a resource into the target bundle, but I'm not sure this is necessarily appropriate. Should copy behavior be changed for Swift playgrounds?
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
Review the discussion in issue #894 and the reported v2.15.1 behavior for Swift playgrounds. Determine whether copying a playground as a resource into the target bundle is expected, then document the decided behavior and its acceptance criteria.
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