onflow / onflow/docs

[Access] Add new gRPC subscription documentation and deprecate old implementation.

Open
#1,150 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
13
Forks
81
PR merge metrics
No merged PRs in 30d

Description

Based on comment from WebSocket documentation PR, the gRPC documentation for subscriptions should also be updated. The old implementation should be marked as deprecated.

Add:

  • SubscribeBlocksFromStartBlockID
  • SubscribeBlocksFromStartHeight
  • SubscribeBlocksFromLatest
  • SubscribeBlockHeadersFromStartBlockID
  • SubscribeBlockHeadersFromStartHeight
  • SubscribeBlockHeadersFromLatest
  • SubscribeBlockDigestsFromStartBlockID
  • SubscribeBlockDigestsFromLatest
  • SubscribeTransactionStatuses
  • SendAndSubscribeTransactionStatuses
  • SubscribeExecutionDataFromStartBlockID
  • SubscribeExecutionDataFromStartBlockHeight
  • SubscribeExecutionDataFromLatest
  • SubscribeEventsFromStartBlockID
  • SubscribeEventsFromStartHeight
  • SubscribeEventsFromLatest
  • SubscribeAccountStatusesFromStartBlockID
  • SubscribeAccountStatusesFromStartHeight
  • SubscribeAccountStatusesFromLatestBlock

Deprecate:

Contributor guide

Open the contributing guide

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.

Research direction

Start with the subscriptions section at developers.flow.com/networks/access-onchain-data and review the linked WebSocket documentation PR comment for context. Document each listed subscription method and mark SubscribeEvents and SubscribeExecutionData as deprecated. Done means the new gRPC methods are covered and the old implementation is clearly labeled.

Written by the indexing model from the issue text.

Assessment

Tech stack
grpc
Domain
api, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.