SwiftPackageIndex-Server
SwiftPackageIndex-Server copied to clipboard
SwiftPackageIndex
The Swift Package Index is the place to find Swift packages!
Rebased version of #1905, to kick off CI and have an Xcode PR view open. To do: - [x] Review/merge review changes #1955 - [ ] Re-run/review query perf tests...
We ran a re-analysis last night, and the feature isn't working as expected. At least it appears not to be! The good news is that there are now 1,763 rows...
There have been a number of invalid URL 500s starting Friday, July 22 morning: - [Rollbar #75](https://rollbar.com/finestructure/SPI-server/items/75) Abort.500: http://spi-prod-docs.s3-website.us-east-2.amazonaws.com/nordicsemiconductor/ios-dfu-library/raw/main/App/fastlane/screenshots/en-US/iPhone 8 Plus-01Devices.png is an invalid URL - [Rollbar #76](https://rollbar.com/finestructure/SPI-server/items/76) Abort.500: http://spi-prod-docs.s3-website.us-east-2.amazonaws.com/nordicsemiconductor/ios-dfu-library/raw/main/App/fastlane/screenshots/en-US/iPhone...
See https://github.com/SwiftPackageIndex/SwiftPackageIndex-Server/pull/1933#discussion_r933990451 Potential bug that might not give wrong results but I suspect it selects N(search view rows) x (N keywords) rows without a join and filters on the product...
As reported by @groue in #1890 (thank you!), packages with multiple project files in the package root will not build as `xcodebuild` does not know which project file to use....
I wasn't aware that the [GitHub README API could respond to different content types](https://docs.github.com/en/rest/reference/repos#get-a-repository-readme) and using that API is a better way to fetch README content than we're currently using...
[`swift-package-catalog`](https://swiftpackageindex.com/kelvin13/swift-package-catalog) is a package that just vends a single plugin, `Catalog`. this causes its Linux builds to fail (since it contains no buildable targets), and ironically, it also causes its...
For example https://swiftpackageindex.com/keywords/networking The collection itself should be available at `https://swiftpackageindex.com/keywords/networking/collection.json` and the visuals for it should be similar in design to how we present author collections, for now.
The name and link for every displayed author should be able to be overridden by our extra metadata file. The *list of contributors* should be custom at this point, and...
Metadata
Owner
Metadata
The Swift Package Index is the place to find Swift packages!