Skip to content

LSIF: GraphQL endpoints for LSIF dumps

Administrator requested to merge lsif-dumps-graphql into master

Created by: efritz

This change exposes endpoints to get LSIF dump metadata from LSIF-server via the GraphQL API.

Changes include:

  • enure visibleAtTip and uploadedAt are exposed and formatted correctly from the LSIF server
  • move the LSIF_SERVER_URL variable definition into a shared space so we can use it from both httpapi and graphqlbackend
  • implement lsifDump(id: ID!): LSIFDump
  • implement lsifDumps(repository: String!, query: String, first: Int, after: ID): LSIFDumpConnection!

The lsifDumps resolver implements forward-only cursor-based pagination. The LSIF server responds with a Link header containing the URL of the next page (if one exists). This (encoded) URL is exposed via PageInfo#endCursor and can be used as the after value of a subsequent request. This is the general method of pagination when interfacing with LSIF-server (we will similarly expose LPS and jobs endpoints via the GraphQL API in the future).

Merge request reports