Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
1 task
bryanchriswhite opened this issue Jul 4, 2024 · 0 comments
Labels
community question Further information is requested

Comments

@bryanchriswhite
Copy link
Contributor

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!]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community question Further information is requested
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant