Also consider "@" when looking for the end of the field name, since
GraphQL directives can follow a field name immediately without any
arguments or aliases being involved. For example:

	query {
		me {
			firstName
			lastName @include(if: $expandedInfo)
		}
	}

The strings.Index check for "@" is the third separator we look for.
There's no reason to look separately, since we just want the first
field name separator.

Add test covering a GraphQL directive that immediately follows the
field name.

Co-authored-by: Dmitri Shuralyov <dmitri@shuralyov.com>
GitHub-Pull-Request: https://github.com/shurcooL/graphql/pull/94

These help generate nicer identifiers in the githubv4 package.

Also remove mention of golint since it's deprecated, and sort
the initialisms map.

* improve the subscription logic and add new settings

* merge reset subscription logic into Run
* fix data race issues and make subscription states immutable

* patch gin v1.7.7 to fix the security issue

Allow using custom HTTP clients (#68)

* support graphql-ws protocol
* add WithConnectionParamsFn method
* add tests and coverage

* docs: clarify usage of structs as variables

* Fix typo in Events section of the readme file

Exposed the jsonutil package with unmarshal json method

Proposing this change to make the example clearer. As a learning gopher, it took me a while to figure this out and I think this change would improve the documentation for many.

* Propagate errors instead of panic

* fix the deadlock issue that the subscription client can't receive error events from the channel.
* close the connection when there is no running subscription
* add a particular error that stops the subscription inside the callback

* update docs for v0.7.0 features

* fix markdown table of content

Co-authored-by: Nizar Malangadan <nizar-m@users.noreply.github.com>

* added method to execute queries already pre-built

* use hyphen tag to skip printing fields to the query string output

add debug mode, expose GraphQL builder functions and UnmarshalGraphQL for unit tests 

update nhooyr/websocket dependencies v1.8.7 to fix the DDoS vulnerability issue

* update README for scalar tag

* Allow tagging of the field as having a scalar GraphQL type

This change allows us to specify that a field in a struct has a
scalar GraphQL type associated with it. This is done by adding
the tag `scalar:"true"` to the field. This would allow us to
- Avoid expansion of the field during request query generation,
  even when the golang type of the field is a struct
- When the response is decoded, the value is simply JSON decoded,
  instead of the much stricter GraphQL decode.
- Types like map[string]interface{}, json.RawMessage, etc should
  work as far as the corresponding fields are marked as scalar

* Handle the error message where we are decoding as json.rawMessage

Co-authored-by: Nizar Malangadan <nizar-m@users.noreply.github.com>