Skip to content

docs: add Which TypeScript package do I need? section - #2

Open
mohadon0 wants to merge 1 commit into
mainfrom
docs/which-ts-package
Open

docs: add Which TypeScript package do I need? section#2
mohadon0 wants to merge 1 commit into
mainfrom
docs/which-ts-package

Conversation

@mohadon0

Copy link
Copy Markdown
Owner

Summary

Fills an immediate documentation gap: new integrators reading docs/integration-guide.md had no guidance on which of the two TypeScript packages (@trustlink/sdk vs @trustlink/contract) to reach for, or why two packages exist at all.

Changes

docs/integration-guide.md

Adds a prominent "Which TypeScript package do I need?" section near the top of the guide (before the first numbered section). The section includes:

  • A decision table: "I want to…" → correct package
  • Explanation of @trustlink/sdk (recommended for most integrators) with a quick-start snippet
  • Explanation of @trustlink/contract (raw auto-generated bindings) with its specific use cases
  • A plain-English explanation of why two packages exist (the read/write split history)
  • A note that a tracked issue exists to unify them, and that @trustlink/sdk is recommended for all new integrations

bindings/typescript/README.md

Adds a callout box at the top pointing to the new guide section and directing most developers to @trustlink/sdk.

sdk/typescript/README.md

Adds a callout box at the top pointing to the new guide section for readers who want to understand the full picture.

Acceptance criteria

  • A new integrator reading docs/integration-guide.md can pick the correct package on the first read without inspecting source code
  • Both package READMEs link to the new section
  • The why-two-packages question is answered
  • The eventual-unification tracking issue is mentioned

Add a prominent package-selection guide to docs/integration-guide.md
explaining the read/write split between @trustlink/sdk and
@trustlink/contract, when to use each, and why two packages exist.

Add a note and link to the guide from both package READMEs so that a
new integrator landing on either README is immediately directed to the
right choice without having to inspect source code.
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.

1 participant