Please support graphql 14

[vicary]

An upgrade to graphql-subscriptions@^1.0.0 should suffice.

[wtrocki]

See https://github.com/aerogear/graphql-mqtt-subscriptions

@davidyaha Our team is maintaining the fork of the library. Would you consider merging the changes from our fork or putting node in the repo.

[davidyaha]

Hey @wtrocki!
I would actually love to merge PRs with fixes for the current issues. As far as I can see, this repo is quite far ahead so it would be problematic to just PR the whole thing.
The first concern would be to update all dependencies and getting renovate/other solutions setup on this repo so it would not become stale again.
Apart from that, do you have any major changes on your repo?

[wtrocki]

Basically, all focused on package updates and ensuring that we support recent versions.
I was about to go and make GraphQL 15 support and was just curious if the upstream library made that changes. I'm using MQTT in production with performance tests etc. so my interest is to maintain this library full time.

[wtrocki]

We also have plans to come up with better way to do filtering based on our tests.

I think we have 3 options:

1. remove fork information from our fork and add info in readme that we are based on https://github.com/davidyaha/graphql-mqtt-subscriptions and continue development.

2. Let you backport some of the changes that you feel are useful and benefit from our work as fork.

3. Figure out how to integrate together into a single library with multiple maintainers.

I do think that option 3 is more preferred, but it all depends on how much involvement you would like to have in this.

[davidyaha]

I think that in the long run, option 3 is preferred of course.
My current projects do not use mqtt unfortunately so any work on my end is spare time based, and also I do not have a solid use case to iterate on.
Do you feel like opening PRs for the changes you make are too cumbersome?
Would you be open to becoming a maintainer here?
Also, option 1 is viable as I think you might want to make changes that are specific to Aerogear. But I would definitely be happy to see any users of this lib benefiting from package updates and improvements that are not specific.

[wtrocki]

Trick is that our repo moved so much and we have added tons of extra things like releases that will not work for your repo, by backporting I will be doing twice work, but we can try.