Mauro Gabriel Titimoli

I'm starting the engines again, the idea is to move forward with the following: 1. Automate release process 2. Migrate to TS / Upgrade deps Once we get here, it...

Graphql spec says error message should be string and there is an extensions field to provide additional context about the error (https://github.com/absinthe-graphql/absinthe-socket/issues/29#issuecomment-1146908311), I would prefer to take this route and...

Below is the comment I wrote in #39: > Message must be string by [spec](https://facebook.github.io/graphql/draft/#sec-Errors). > > We could consider adding support to [extensions](https://facebook.github.io/graphql/draft/#example-fce18).

In the coming days, I will be sending an update that automates the release process, so we can start moving the engines again.

However regarding to this specific topic, the spec says the message must be [string](https://spec.graphql.org/June2018/#sec-Errors), and there is an extensions field to provide additional context about the error.  

Hi @G3z, You will need to create a wrapper link on top of socket-link to do this. It will have to be somekind of a memoized factory, where it will...

Nice hack @G3z, but it won't reconnect to socket if auth changed. The proper way to handle this would be to introduce an extra level of indirection, so instead of...

The way I've just commented will introduce a breaking change, that's why I'm still doubting if it is the best way or we should create another factory fn for this...

Hi everyone, The easiest way to deal with this, is to create a new link on top of the one provided here, that can keep in its internal state the...

Hi @maxbrunsfeld, I understand your point, but I believe in the meantime until that you mentioned happens, this package shouldn't break the other stuff around. I had a hard time...