v1.4.1

What's Changed

• feat(exec): Use alias provided by client for duplicated fields by @yudiharibowo in #28

Full Changelog: v1.4.0...v1.4.1

v1.4.0

What's Changed

• feat(exec): Duplicate only fields requested by client by @yudiharibowo in #27

Full Changelog: v1.3.9...v1.4.0

v1.3.9

What's Changed

• feat(query): Bypass auto duplicate fields by @yudiharibowo in #26

Full Changelog: v1.3.8...v1.3.9

v1.3.8

What's Changed

• feat(exec): JS Limitation of int64, make str duplicate by @yudiharibowo in #25

Full Changelog: v1.3.7...v1.3.8

v1.3.7

What's Changed

• feat(panic): log query that causing the panic by @yudiharibowo in #24

New Contributors

• @yudiharibowo made their first contribution in #24

Full Changelog: v1.3.6...v1.3.7

Fork Syncup with Master till Aug 2022

This PR is for syncing up with latest(Aug 1, 2022) from https://github.com/graph-gophers/graphql-go.
Changes
Pulled Latest Commit from graphql-go master. (Support for extensions was update)
In this PR we readded the custom change lost due to update like int64 support.
All the changes are added in the doc https://docs.google.com/spreadsheets/d/1oS-bELuMp7Xq5-TDGciS617omD_bfr09UAK0IaHyVWA/edit?usp=sharing

Adding Int64 support for input param

Adding Int64 support for non struct input param

Return query names as well while validating query

Using graphql-go parser only to get the query names from the query string.

Handle Malformed GraphQL Requests

We will be adding handling for malformed requests coming to gqlserver by returning a boolean value from graphql.go which indicates whether the error rose during parsing phase(meaning malformed query) or during validation phase.

Handle Malformed GraphQL Requests

We will be adding handling for malformed requests coming to gqlserver by returning a boolean value from graphql.go which indicates whether the error rose during parsing phase(meaning malformed query) or during validation phase.