[Investigate] Feasibility of using gqlgen for go types from schema.graphql

[bryanchriswhite]

Objective

Investigate the feasibility of using gqlgen to generate go types which are sufficient for use with go-pg's DB.Model() API.

Origin Document

Foundational.

Goals

• Streamline effort required to add and maintain E2E go test suites.

Deliverables

• Add a comment in this issue which includes the results of the investigation, sufficient to answer questions like:

1. Can gqlgen handle the subquery schema.graphql (it may contain extra syntax, like @entity and @json).
   1a. If no, is there an alternative that is?
2. Are gqlgen's (or an alternative) generated types compatible with go-pg's DB.Model API?
   2a. If no, is there an alternative to go-pg which offers a similarly simplistic interface for querying and deserializing data from postgres.
   2b. If no, what is the level and shape of effort required to bridge the gap between generated go types and go-pg's lower-level APIs (e.g. DB.QueryContext()).

Non-goals / Non-deliverables

• Any code or dependency updates (investigation only).

---

Creator: @bryanchriswhite
Co-Owners: [sign up here!]