Why are local packages added using XcodeProj and local packages added through the Xcode GUI interface in different locations in the project? Do we need to distinguish between locally added and remotely added packages?
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.2k
- Forks
- 355
- Avg merge
- 5h 48m
- Merged PRs (30d)
- 13
Description
Context 🕵️♀️
Provide information that helps with understanding your issue. For example your use case that the project doesn't cover, what you were doing when you found the bug... You can also provide the version of the library that you were using, how you integrated it with your project, the platform version...
Use the following two methods to add packages
`
//remote package
do{
let reference = try rootObject.addSwiftPackage(repositoryURL: package.url, productName: package.name, versionRequirement: .branch(""), targetName: "TestSwiftPackage")
print("success===(reference)")
} catch {
print("fail (package.name),error:(error.localizedDescription)")
}
// local package
do {
let reference = try rootObject.addLocalSwiftPackage(path:Path(package.url), productName: package.name, targetName: "TestSwiftPackage")
print("success===(reference)")
} catch {
print("fail (package.name),error:(error.localizedDescription)")
}
`
but remote package and local package in different localtion.
What 🌱
Describe here your issue, a bug you found, an idea that you had, something that you think can be improved...
Proposal 🎉
Attach your own proposal (if you have it). We'll discuss in on the issue to find the best one that fits into the library.
Contributor guide
No contributing guide indexed for this repository
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 comparing the rootObject.addSwiftPackage and rootObject.addLocalSwiftPackage entry points and inspect the generated project locations shown in the report. Determine whether the differing locations are expected, then document the distinction or define the desired behavior before implementation; the issue provides no named files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100