In Xcode 15.4, SPM now auto-generates Swift symbols for catalog assets.
That's great! Except they're declared internal, therefore they're useless in a package whose sole purpose is defining a Design System 😕
@layoutSubviews@tonyarnold But the package manifest could have a way to declare the scope of certain resources. That would be very nice for the design system use case.
@layoutSubviews@tonyarnold I actually think it’s a good decision, much like making all other types internal and leaving it up to the package author to define scope. I don’t think it would be a good idea to openly expose all assets, since there may be considerations to what you want to expose, how an asset is meant to be used, etc. I use to create public, static image extension properties for the assets I expose from a package. It also lets you redesign how an asset is resolved at a later time.
@harshil the way software is built/linked inside Apple is totally different from what 3rd party devs use. No surprise nobody notices these glaring omissions.
@david@harshil the thing is, they don’t. Everything is delivered in a giant nightly SDK you install first thing in the morning while sipping a cup of coffee.
If you really need to use something another team just made that day, you install a “root” which is just a tarball overwriting the relevant files in the SDK.
Gross? Yeah. Does it matter? No, tomorrow morning you wipe it all off and install a fresh SDK anyway.
@layoutSubviews Ah I see. ColorResource vs Color? In the app's Asset catalog I see them generated under Color directly. That doesn't seem to happen in Packages.
Add comment