Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Implementation-independent type of the query field in the subscribe message
See original GitHub issueHello, we have been looking for an alternative protocol to subscriptions-transport-ws and found this repository which looks very promising and far more mature.
The only problem is the query type in the subscribe message that seems to be javascript specific as the DocumentNode is part of internal classes of graphql-js, and our server is written in Java. Do you plan to make the protocol more open for other languages that use only the string query representation of GQL query in GQL library public API?
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I have made #45, but I am still not completely on board… There are some pros and cons in the description there.
Would be cool if you could make this argument at the GraphQL over WebSocket PR. Hearing more opinions would be a smart move when faced with making a decision like this.
🎉 This issue has been resolved in version 1.10.0 🎉
The release is available on:
Your semantic-release bot 📦🚀