stash/vendor/github.com/vektah/gqlparser/v2
WithoutPants 30809e16fa
Update go dependencies (#3480)
* Bump golang.org/x/text from 0.3.7 to 0.3.8

Bumps [golang.org/x/text](https://github.com/golang/text) from 0.3.7 to 0.3.8.
- [Release notes](https://github.com/golang/text/releases)
- [Commits](https://github.com/golang/text/compare/v0.3.7...v0.3.8)

---
updated-dependencies:
- dependency-name: golang.org/x/text
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

* Update go dependencies

* Update x/net

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-28 08:26:14 +11:00
..
ast Update go dependencies (#3480) 2023-02-28 08:26:14 +11:00
formatter Update go dependencies (#3480) 2023-02-28 08:26:14 +11:00
gqlerror Support Go 1.18: Upgrade gqlgen to v0.17.2 (#2443) 2022-04-02 18:08:14 +11:00
lexer Update go dependencies (#3480) 2023-02-28 08:26:14 +11:00
parser Update go dependencies (#3480) 2023-02-28 08:26:14 +11:00
validator Update go dependencies (#3480) 2023-02-28 08:26:14 +11:00
.gitignore Stash box client interface (#751) 2020-09-17 19:57:18 +10:00
gqlparser.go Update go dependencies (#3480) 2023-02-28 08:26:14 +11:00
LICENSE Stash box client interface (#751) 2020-09-17 19:57:18 +10:00
readme.md Support Go 1.18: Upgrade gqlgen to v0.17.2 (#2443) 2022-04-02 18:08:14 +11:00

gqlparser CircleCI Go Report Card Coverage Status

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, 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 reference implementation.