Skip to content

Evaluate different GraphQL implementations #47

@eaceaser

Description

@eaceaser

So, I'm really not a fan of the fact that the current GQL library we're using is not type safe. Also it hasn't seen much development for a while, which is a bit concerning given that GQL is a relatively new protocol. Also according to some old benchmarks, the library we're using is slower than the alternatives by an order of magnitude. We should confirm that result.

This uses code generation, so there will be an additional build step to generate the code. However, it generates typesafe code. I'm not the world's biggest fan of code generation, but this is golang and that pattern is used in various places.

Parses a schema file, which I kinda like. Has type-safe arguments.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions