2.3.0

• Added the ability to pass a payload to the initialization phase and thereby enabling authenticated ws endpoints (#99)
  • Thanks to @rs-anders-agren

2.2.0

• Enums serialized according to spec (#77)
• Cancellation tokens support (#90)
  • Thanks to @bddckr
• Support HttpClientFactory (#83)
• Reconnecting support for subscription client (#81)
• Support directives (#74)
• Support for selecting only partial fields to request from a query (#78)
• Subscription errors was not being caught i deserializer was throwing a exception (#92)
• Support for selecting the specific field where a argument should be applied
• Additional validation rules for the GraphQL query validator

2.1.1

• Schema validation fails when fields are nullable (#91)

2.1.0

• Method for allowing ClientWebSocket to be supplied in constructor to for example support secure websockets (#68 #72)
  • Thanks to @chelliwell
• Support specifying that a argument only applies to a specific field (#75)
• Disconnect event on subscription client (#76)
• Introspection query (#60)
• Validate queries against introspection (#59 #80)

2.0.1

• Updated OperationMessage to be compliant with GraphQL subscriptions-transport-ws (#67)

2.0.0

• Added subscription client
• It's now possible to add headers per request or by accessing the HttpClient from the IGraphQLHttpExecutor (#63)
• Support for Unions and Interfaces
• Refactoring of client

2.0.0-beta5

• More documentation in subscription client
• Refactoring of subscription client

2.0.0-beta4

• Support C# interfaces used for GraphQL interfaces
• Removed not needed GraphQLDataDetailedResult since it was a duplicate of GraphQLDataResult
• Added AdditionalData such additional fields is supported for GraphQLDataError, GraphQLDataErrorLocation and GraphQLDataResult
• Removed IGraphQLField, IGraphQLArguments and IGraphQLTargetType
• Updated subscription client and added testcase

2.0.0-beta3

• Expose response headers through a new ExecuteDetailed method (#66)

Thanks to @Jasonfran

1.4.0

• Expose response headers through a new ExecuteDetailed method (#66)

Thanks to @Jasonfran