Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Quick Start: credential offers never define the schema URL from the saved GUID

Aperta
  • Qualcosa non va?
#292 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
68/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Ambito
documentation

Direzione di ricerca

Start with documentation/develop/quick-start.md, tracing the saved schema GUID at lines 153–156 to the schemaId fields in both issuance tabs at lines 598–600. Read the Agent 2.0.0 schemaId annotation and raw-schema endpoint linked in the issue to confirm the expected URL shape and agent context. Update the guide so readers can construct and reuse a reference to the created schema, then verify it against the stated acceptance criteria.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug documentation ready-for-agent

User impact

A developer reaches issuance with only a saved schema GUID, then must supply an undefined [[schemaId]]. A bare GUID is not the dereferenceable schema reference required by the pinned Agent.

Affected documentation and ownership

  • Page: Quick Start Guide, GET 200 at 2026-10-28 20:48:50 UTC; affected source text is also deployed.
  • Editable owner: hyperledger-identus/docs, local hand-authored documentation/develop/quick-start.md at fa985dfa33caefa45bf1e9009e1f6f5a445344fb; not imported SDK content or generated API output.
  • Intended versions: page environment pins select Agent 2.0.0 (5865d9470dc5ce6631aec780e7cf63d4f454555a); SDK checkout selects v6.6.0 (1a9da8135ec5745bca182904f0a1703d7be6d1a2). Matching pins, not latest releases, govern this comparison.
  • Affected text: Save the schema GUID → use schemaId in credential offers (both issuance tabs).

Observed versus expected

The schema step says to capture guid for further steps. Both offer bodies later contain "schemaId": [[schemaId]], but neither defines that variable or explains how the GUID becomes a schema URL. Expected: a reader can obtain the usable reference to the just-created schema, including an appropriate reachable base URL, and reuse it consistently. This missing dataflow step is distinct from JSON quoting.

Evidence and reproduction

  1. Follow the linked page statically from schema creation to either offer. The substitution list defines other inputs, not schemaId.
  2. The pinned schemaId annotation requires a JSON-schema URL, with an example ending in /cloud-agent/schema-registry/schemas/{guid}/schema; the raw-schema endpoint corroborates that path.
  3. The compatibility parser carries the supplied string unchanged. Claim validation uses schema dereferencing and GenericUriResolver; there is no GUID-to-URL expansion. A schemeless GUID cannot be resolved there.

No HTTP error code, actual network reachability or successful issuance is claimed.

Verification used Python 3.13.15 text/HTML inspection of immutable public sources and deployed text. No repository code, compiler/build, service request or browser test was run; deployment commit identity is not exposed.

Existing work checked

Fully paginated open/closed issue-and-PR inventories in docs, cloud-agent and sdk-ts, plus title/body/comment searches by page/component/root cause and relevant discussion/patch reads. docs #222/PR #223 pinned versions and added schemaId but never defined this mapping. docs #202 concerns VCDM API migration; the compatibility field is still accepted at the intended version. cloud-agent #1213 concerns generated API examples mixing AnonCreds/W3C schema formats, not this portal-local missing step. GUID/schemaId and Quick Start searches found no matching open repair.

Acceptance criteria

  • A reader with the preceding schema response can fill the schema reference in both issuance tabs without guessing its construction.
  • Validate the documented reference against Agent 2.0.0: it resolves to the intended schema from the required agent context and is used consistently in the subsequent flow.
Lingua principale
TypeScript
Stelle
15
Fork
8
Merge medio
3g 14h
PR unite (30g)
2

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di hyperledger-identus/docs

Tutte le issue di hyperledger-identus/docs

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.