Skip to content

Conversation

@codewalkerdan
Copy link

Not just authorization, but other headers could be added that may be required when initializing a web socket connection.
It supports adding authorization tokens

/// The payload of the websocket request
/// </summary>
public GraphQLRequest Payload
public object Payload
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

breaking change

<Description>GraphQL basic types</Description>
<RootNamespace>GraphQL</RootNamespace>
<TargetFrameworks>netstandard2.0</TargetFrameworks>
<Version>1.0.0</Version>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

?

<PropertyGroup>
<TargetFrameworks>netstandard2.0;net461</TargetFrameworks>
<RootNamespace>GraphQL.Client.Http</RootNamespace>
<Authors>Deinok,Alexander Rose,graphql-dotnet</Authors>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

@sungam3r sungam3r left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These edits don't seem right to me.

@rose-a
Copy link
Collaborator

rose-a commented Oct 7, 2020

@codewalkerdan Thanks for your contribution. I'm closing this in favor of #294, which basically does the same thing albeit keeping types and names close to the Apollo GraphQL over WebSocket Protocol Spec, which this library aims to fully implement.

@rose-a rose-a closed this Oct 7, 2020
@codewalkerdan
Copy link
Author

Sorry for not replying. I have little time, but thank you for the feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants