Unhandled Info.plist when importing with SPM

[sbertix]

Hey @omaralbeik,

amazing job with this library 💪

I've found an issue when using Drops with the SPM:

Possible fixes would be moving the Info.plist out of the Sources folder – as it's only used in the test-wrapper app, or explicitly excluding it from Package.swift target.
I'd push a PR but I'm not really sure which approach you'd rather follow 😅

[omaralbeik]

Thanks @sbertix, both are valid options, I'm leaning a little bit toward ignoring the file in Package.swift, what do you think?

[sbertix]

It definitely makes sense in the short run, but I feel like it's not extremely intuitive to have the Info.plist for the test app with the actual src.
It's confusing, other than adding one step to people maybe wanting to drop the actual folder directly in their project (being a small library) — cause such people will always exist hahaha

I would argue that even having the actual project file for the test app at root level might give the wrong impression on the scopes of the library itself ("is this a library? Is this an app?") and it would probably make more sense hidden inside the Tests directory, together with its Info.plist, referencing the Sources directory either through header paths or even as a local SPM dependency.

I understand this is, however, although an easy "fix", far beyond the scopes of the actual issue here 😅
Sorry hahaha

[omaralbeik]

Nice, I actually like the idea of removing the Xcode project from the root directory

[omaralbeik]

I merged the PR to release a quick patch, feel free to open another PR with the proposed changes above