Quick Start: TypeScript mediation example calls ConnectionsManager with missing arguments
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- documentation
Research direction
Read the TypeScript mediation example in documentation/develop/quick-start.md (lines 375–402) and compare its ConnectionsManager call with the constructor in the pinned SDK v6.6.0 source, src/edge-agent/connectionsManager/ConnectionsManager.ts. Update the example to supply the required dependencies, then verify against that constructor that the handler is defined and the call type-checks.
Written by the indexing model from the issue text.
Description
User impact
Developers copying the Quick Start's "establish mediation when building your own application" TypeScript example cannot construct the connection manager at the SDK version the page itself selects. The call supplies four arguments, so the mediator handler is passed into the Pollux position and the required mediation-handler argument is missing. Starting the agent then reaches mediation setup with an undefined handler instead of a working manager.
Affected documentation and ownership
- Page URL and observed deployment/time: https://identus.io/documentation/develop/quick-start/ — GET 200 (after a 301 from the no-slash form) on 2026-10-29T16:56:40Z; the deployed HTML contains the same snippet.
- Documentation source permalink and revision: documentation/develop/quick-start.md, TypeScript mediation example lines 375–402 (defective call at line 388), revision
fa985dfa33caefa45bf1e9009e1f6f5a445344fb. - Editable owning source: the same file in
hyperledger-identus/docs. Hand-authored portal Markdown, not imported SDK documentation or generated API output. - Intended component version and evidence establishing it: the page's SDK checkout instructions select tag v6.6.0 (quick-start lines 216–220), which resolves to commit
1a9da8135ec5745bca182904f0a1703d7be6d1a2. The page selects no other SDK version for this snippet.
Observed versus expected
The page example calls:
const manager = new SDK.ConnectionsManager(castor, mercury, pluto, handler);
At the selected v6.6.0 commit, ConnectionsManager requires five positional dependencies before the optional arguments (ConnectionsManager.ts lines 70–78):
constructor(
public castor: Castor,
public mercury: Mercury,
public pluto: Pluto,
public pollux: Pollux,
public mediationHandler: MediatorHandler,
public pairings: DIDPair[] = [],
public options?: AgentOptions
)
With the page's four arguments, handler binds to pollux, and mediationHandler is undefined. The manager's startMediator() calls this.mediationHandler.bootRegisteredMediator().
Expected: the example supplies the dependencies the selected SDK requires, so the copied code type-checks and agent start can begin mediation.
The rest of the snippet is consistent with v6.6.0: SDK.Agent resolves to edge-agent/didcomm/Agent (src/index.ts lines 10–11), whose constructor takes apollo, castor, pluto, mercury, mediationHandler, connectionManager, seed, ... (Agent.ts lines 62–72). The defect is the manager construction, not a comparison against an unrelated base Agent class.
Evidence and reproduction
Static comparison at immutable revisions, observed 2026-10-29T16:57:35Z:
- Read the page snippet in the current source at
fa985dfand in the saved deployed HTML. - Read the v6.6.0
ConnectionsManagerconstructor andstartMediator()inhyperledger-identus/sdk-tsat1a9da81. - Count the page's arguments (4) against the constructor's required parameters (5).
Limitations: no TypeScript compiler, build or agent run was executed. Execution was blocked because no disposable credential-free check environment was established. This is a source-level contradiction with the page's own selected version, not a runtime trace.
Existing work checked
Searched open and closed issues and PRs in hyperledger-identus/docs (full title inventory of 62 issues and 238 PRs) and in hyperledger-identus/sdk-ts, by ConnectionsManager, Pollux, mediation, code example and quick start, and read matching bodies and discussion.
- The seven open Quick Start issues #290–#296 cover startup paths, schema examples, offer/response IDs, demo controls and manual issuance attribution; none covers this mediation constructor snippet.
- sdk-ts PR #394 (
feat!: refactor ConnectionManager) is the SDK-side API change that the portal example did not follow; it is not a documentation repair. - No open issue or PR repairs this example.
Acceptance criteria
- The TypeScript mediation example constructs
ConnectionsManagerwith the dependencies required by the page's selected SDK version. - Verification against the pinned v6.6.0 source, or a type-check/build in a disposable environment, shows the example compiles and reaches mediation setup with a defined handler.
- Dominant language
- TypeScript
- Stars
- 15
- Forks
- 8
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hyperledger-identus/docs
-
bug documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
hyperledger-identus/docs#303 ·
-
bug documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
hyperledger-identus/docs#301 ·
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hyperledger-identus/docs#299 ·
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
hyperledger-identus/docs#298 ·
-
bug documentation
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
hyperledger-identus/docs#297 ·
All issues in hyperledger-identus/docs
Similar issues
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
hemi-earn
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
vetro-protocol/vetro-monorepo#1043 ·
Maintainers usually reply within 1 day
-
stage 2: bare names resolve against PATH differently from the shell (empty and relative entries)Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
STRML/omp-classifier#206 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
atlassian-labs/mermaid-diagrams-viewer#188 ·
Maintainers usually reply within 1 day
-
dashboard enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Olanetsoft/agent-lookout#225 ·
Maintainers usually reply within 1 day