Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Alternative for GraphQL Subscriptions over WebSocket

Open
#5 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
graphql, typescript

Research direction

No files, tests, or entry points are named. Start by locating the graph-node WebSocket subscription transport and reviewing the two proposed alternatives: subscribe-as-query and query plus hook. Clarify which approach should be implemented and what reliability and completion criteria apply before beginning work.

Written by the indexing model from the issue text.

Description

experiment

Today, graph-node Subscriptions transport is not 100% reliable and uses a legacy protocol.

We are looking into different ways of providing an alternative to that.

Possible solutions:

  • subscribe-as-query: write a GraphQL Subscription, but choose a custom hook (Smart contract event? just polling?)
  • query + hook
Dominant language
TypeScript
Stars
186
Forks
49
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from graphprotocol/graph-client

All issues in graphprotocol/graph-client

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.