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

Go SDK: wholesale feed mirror helper for products/signals

Open
  • Is something wrong?
#286 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
api, backend

Research direction

Start with the Go SDK’s existing API patterns and the TypeScript shape tracked in adcp-client#2094; the issue does not name Go files or tests. Map the product and signal bootstrap, refresh, notification routing, bulk-change handling, persistence, and sync_accounts registration requirements, then use the listed unit tests and training-agent storyboards in adcp#5056 to check behavior. Done means the mirror helper and its receiver usage example cover those flows.

Written by the indexing model from the issue text.

Description

claude-triaged enhancement go-first-class sdk

Context

This is the Go follow-up for the current 3.1 wholesale-feed model, replacing the stale CatalogSync shape tracked in adcp#4789. The protocol no longer has separate /catalog/events or /catalog/subscriptions endpoints.

Current surface:

  • bootstrap via get_products with buying_mode: "wholesale" and get_signals with discovery_mode: "wholesale"
  • persist wholesale_feed_version and cache_scope per connected agent/account
  • refresh with if_wholesale_feed_version; unchanged feeds return unchanged: true
  • register receivers through account-level sync_accounts.accounts[].notification_configs[]
  • process product.*, signal.*, and wholesale_feed.bulk_change notifications

Request

After the TypeScript API shape stabilizes in adcp-client#2094, port an idiomatic Go helper for maintaining a local mirror of wholesale product/signal feeds.

Suggested scope:

  • Context-aware bootstrap and refresh API for product and signal wholesale feeds.
  • In-memory indexes keyed by agent URL/account plus product or signal id.
  • Version/cache-scope tracking with conditional refresh support.
  • Optional persistence interfaces for stored versions/index state.
  • Channel or callback-based event hooks for wholesale-feed webhook notifications.
  • Re-bootstrap the affected feed on wholesale_feed.bulk_change, using affected_entity_type to choose product vs signal.
  • Helper for registering notification_configs[] through sync_accounts.
  • Docs or example showing receiver plus mirror usage.

Tests

  • Unit coverage for conditional refresh, unchanged responses, re-bootstrap on bulk change, and product/signal notification routing.
  • Integration coverage against the training-agent storyboards from adcp#5056 where practical.

Related

  • adcp#4789 — stale umbrella issue, superseded by repo-specific SDK trackers
  • adcp-client#2094 — TypeScript source-of-truth tracker
Dominant language
Go
Stars
4
Forks
2
Avg merge
1d 19h
Merged PRs (30d)
14

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 adcontextprotocol/adcp-go

All issues in adcontextprotocol/adcp-go

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.