You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please explain what data is incorrect and what you expected to see
This package actually does have dependencies, but there's Funny Business going on in the Package.swift, and I have no doubt that's the issue.
Additional context
It's definitely interesting food for thought that dependencies definitely do not have to be a constant across platforms. I would not be surprised to discover that this kind of per-platform dependency management isn't that uncommon when supporting Apple/non-Apple platforms.
I suspect you're already aware of this problem on some level, but I couldn't find an existing issue with my 10 seconds of effort.
The text was updated successfully, but these errors were encountered:
Yeah, I think this is because we run all package analysis commands on Linux. I wish package manifests weren't executable and platform dependent 😕
I'm not sure what we could do about it. We'd have to guess or somehow determine what the "main" platform is.
We could take the highest number but then we'd disadvantage a package if there's a particular, perhaps rarely used platform that requires additional dependencies.
The only correct way of doing it would be to report dependency count per platform, I guess. We could at least tooltip a per platform breakdown like we do for the Swift 6 compatibility.
I wonder though how common a problem this actually is 🤔
Which package(s) are showing incorrect data?
Please explain what data is incorrect and what you expected to see
This package actually does have dependencies, but there's Funny Business going on in the Package.swift, and I have no doubt that's the issue.
Additional context
It's definitely interesting food for thought that dependencies definitely do not have to be a constant across platforms. I would not be surprised to discover that this kind of per-platform dependency management isn't that uncommon when supporting Apple/non-Apple platforms.
I suspect you're already aware of this problem on some level, but I couldn't find an existing issue with my 10 seconds of effort.
The text was updated successfully, but these errors were encountered: