I’ve been kicking the wheels on Xcode 12 and its potential to make use of frameworks and packages with playgrounds. Up till now, I’ve solely been in a position to import packages which might be both downloaded or developed regionally on my dwelling system. Nevertheless, lots of the packages I need to work with are hosted from GitHub.
I made a decision to comply with a hunch and see if I may import my dependency by an area Forwarding package deal after which use that code. Lengthy story quick: I may.
Right here’s my playground, efficiently operating.
The RuntimeImplementation
is asserted in a GitHub-hosted package deal known as Swift-Common-Utility:
What I did to make this work was that I created what I known as a Forwarding Utility, whose sole job is to create a shell package deal that depends upon the distant package deal and forwards it to the playground. It appears like this. It’s a single file known as “Forwarding.swift” (no, the identify is under no circumstances magic.) in Sources/. I take advantage of @_exported
to ahead the import.
/* Use this to ahead web-based dependencies to Swift Pkg */ @_exported import GeneralUtility
Its Package deal.swift installs the dependency:
dependencies: [ .package(url: "https://github.com/erica/Swift-General-Utility", .exact("0.0.4")), ], targets: [ .target( name: "ForwardingUtility", dependencies: [ .product(name: "GeneralUtility"), ], path: "Sources/" ), ],
And that’s just about all that there’s to it, aside from (as I discussed in my different publish about easy methods to use SwiftPM packages in playground workspaces) that you could have to stop and re-open the primary beta earlier than you’ll be able to import the forwarding.
Let me know something that I tousled. But in addition let me know if this was useful to you!