https://github.com/vektah/gqlparser

A port of the parser from graphql-js into golang
https://github.com/vektah/gqlparser

Last synced: 3 days ago
JSON representation

A port of the parser from graphql-js into golang

• Host: GitHub
• URL: https://github.com/vektah/gqlparser
• Owner: vektah
• License: mit
• Created: 2018-05-06T02:24:25.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2025-01-13T23:53:00.000Z (12 days ago)
• Last Synced: 2025-01-15T08:08:35.386Z (11 days ago)
• Language: Go
• Size: 1.08 MB
• Stars: 509
• Watchers: 12
• Forks: 125
• Open Issues: 34
• Metadata Files:
  • Readme: readme.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-ccamel - vektah/gqlparser - A port of the parser from graphql-js into golang (Go)
• awesome-list - gqlparser - js into golang | vektah | 284 | (Go)

README

        
gqlparser [![CircleCI](https://badgen.net/circleci/github/vektah/gqlparser/master)](https://circleci.com/gh/vektah/gqlparser) [![Go Report Card](https://goreportcard.com/badge/github.com/vektah/gqlparser/v2)](https://goreportcard.com/report/github.com/vektah/gqlparser/v2) [![Coverage Status](https://badgen.net/coveralls/c/github/vektah/gqlparser)](https://coveralls.io/github/vektah/gqlparser?branch=master)

===

This is a parser for graphql, written to mirror the graphql-js reference implementation as closely while remaining idiomatic and easy to use.

spec target: June 2018 (Schema definition language, block strings as descriptions, error paths & extension)

This parser is used by [gqlgen](https://github.com/99designs/gqlgen), and it should be reasonably stable.

Guiding principles:

 - maintainability: It should be easy to stay up to date with the spec

 - well tested: It shouldn't need a graphql server to validate itself. Changes to this repo should be self contained.

 - server agnostic: It should be usable by any of the graphql server implementations, and any graphql client tooling.

 - idiomatic & stable api: It should follow go best practices, especially around forwards compatibility.

 - fast: Where it doesn't impact on the above it should be fast. Avoid unnecessary allocs in hot paths.

 - close to reference: Where it doesn't impact on the above, it should stay close to the [graphql/graphql-js](https://github.com/graphql/graphql-js) reference implementation.