vapor-community / packagecatalogapi

A replacement for the IBM Swift Package Catalog.

PackageCatalogAPI

A description of this package.

packagecatalogapi's Issues

Internal server error if search would return no results

example:
https://package.vapor.cloud/packages/search?name=asdfasdfsdfasdf&limit=10
returns

{
    "reason": "Something went wrong.",
    "error": true
}

GraphQL usage

I'm curious about the choice of GraphQL and using Github's API. What kind of benefit are you trying to get out of using GraphQL? (and "I thought it'd be an interesting technology to use" I totally understand)

I also notice that your queries are built as multiline strings with hand-corrected indenting, etc. It looks like there are a couple GraphQL Swift libraries that could be used here, or forked if they need updating. Do any of those look useful?

Roadmap

I'd like to contribute, but I'm not sure about how/where to get started:

1. What's the vision for what this turns into? Is it similar to cocoapods.org, or rubygems.org?
2. Is there a roadmap for pieces that need to be built?

Features needed for the ether frontend

Repo id exposed in search // looks like this one may already exist
Ability to get more info about a repo by querying by id. Should include link to/contents of README