@swift-ci create

The `exclude` parameter solely has an effect on the build, not on which files are shown in Xcode. Xcode will currently always show any files that are part of the directory tree that contains the package manifest (with some limited exceptions, e.g. we won't show .xcodeproj files).

Comment by Ariel Elkin (JIRA)

@neonichu I see now. I find this counterintuitive.

When Xcode opens an .xcodeproj file it only displays the files included therein. This is intuitive, as you'd expect to see just the files included in the Xcode project.

So I would expect Xcode to behave analogously when opening a Package.swift file. It should just display files explicitly marked as being part of the package, and not display files explicitly marked as NOT being part of the package. In addition, showing excluded files in Xcode leads to unnecessarily higher cognitive load (a package's directory can include files irrelevant to the package itself such as ci scripts, derived data folders, ancillary files from other dependency managers. All these will bloat Xcode's UI)

Please consider amending the current behaviour, or updating the docs for `exclude`

Seconded! I am the developer of a free and opensource library and I find this to be very annoying.

For Cocoapods support this issue doesn't appear for our users. For SPM support it does.

My first reaction and others from my users was this was a huge issue for our Swift package.

Is there any way to prioritize this? @neonichu @tomerd @shahmishal

Thanks!

@neonichu this seems to be more of an Xcode level issue, correct?

Yep, this is entirely about what is shown by the project navigator in Xcode.

is there better way to track this then? maybe apple feedback?

Opened a ticket on Feedback Assistant. Ticket ID: FB11422233 (Issue with Swift Package Manager)

@neonichu @tomerd - thank you for both of your prompt responses.

It means a lot for the opensource community. Let us know if there is any way we can help or to escalate this issue.

Benyam

I recently faced a similar issue. I ended up using a workaround posted here to use an empty Package.swift file like so:

// swift-tools-version:5.5

import PackageDescription

let package = Package()

@setoelkahfi is this issue reproducible for you only in Xcode or with command-line invocations of SwiftPM too?