Skip to content

feat(context): support array of networkIds for multi-network scoping#178

Open
manjudr wants to merge 3 commits into
draftfrom
feat/network-id-multi-network-support
Open

feat(context): support array of networkIds for multi-network scoping#178
manjudr wants to merge 3 commits into
draftfrom
feat/network-id-multi-network-support

Conversation

@manjudr

@manjudr manjudr commented Jun 12, 2026

Copy link
Copy Markdown
Collaborator

Extended context.networkId to accept either a single string or an array of strings, enabling a Provider Node to publish a catalog to multiple networks simultaneously and a Consumer Node to scope discovery across multiple networks. A bare string is treated as a single-element array — no breaking change for existing publishers.

For more details refer to the discussion: Networks-for-Humanity/fabric-support#24

manjudr added 3 commits June 12, 2026 11:37
context.networkId now accepts either a string or an array of strings.
A bare string remains valid and is treated as a single-element array,
preserving full backward compatibility for existing publishers.

Use case: a Provider Node can publish a catalog to multiple networks
simultaneously, and a Consumer Node can scope a discovery request
across multiple networks, by supplying an array of network identifiers.

Closes: Networks-for-Humanity/fabric-support#24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support context.networkId as an array — filter catalogs across multiple networks

1 participant