Explore additional package metadata
Closed this issue · 4 comments
As wished for by Taylor Swift kelvin13ma@gmail.com on swift-users.
I really like this idea, however what I really want to know about a package usually includes: does it support my platform, does it depend on Foundation, what other modules it depends on, what versions of Swift it builds on (including nightly builds), and how well its documented. I don’t know how this can be done by simply querying github’s API though, it’s bound to require at least some involvement on the part of the package author.
Unfortunately most of this (pretty much everything besides #16) isn't quite possible with the current design of apodidae, but this issue is for discussion and for not forgetting about it.
Can the swift version be reliably pulled from the manifest? A swift-tools-version comment could be used as it currently already is used by SwiftVersion, but the fallback to Swift 3 is irritating in this case. And is the swift-tools-version always up to date with a package's supported tooling?
But wasn't it also possible to specify the supported Swift version in the manifest (starting with 4 I think). Is that checked by the compiler and can thus be trusted?
CI state is available via GH's API. Also, it was suggested to possibly read badges/shields from repo READMEs. Things like supported platforms etc.
Repo topics might add some more value.
Just going to take whatever swiftpm.co adds.