Skip to content

docs: narrow scope to protocol-only transport#3

Merged
Taure merged 1 commit into
mainfrom
docs/scope-narrow-protocol-only
May 2, 2026
Merged

docs: narrow scope to protocol-only transport#3
Taure merged 1 commit into
mainfrom
docs/scope-narrow-protocol-only

Conversation

@Taure
Copy link
Copy Markdown
Contributor

@Taure Taure commented Apr 30, 2026

Summary

The previous README claimed full coverage of worlds, terrain, voting, economy, leaderboards, social, tournaments, and storage as stable features. The actual implementation is a thin WS+codec library with scaffolded typed REST helpers — and the architectural direction is to drop those helpers as the SDK narrows to a protocol-only transport, mirroring `asobi-lua-client`.

This PR is a credibility patch: rewrite the README to reflect the real and intended scope. No code change here; the code refactor (deleting the typed REST modules, dropping the unimplemented WS event types) follows in a separate PR.

Changes

  • Replace "Features" matrix that claimed 9 stable subsystems with a scope statement: transport, codec, reconnection, session resume, RPC, pubsub
  • Add an explicit "Status" section calling out v0.x typed REST helpers as deprecated
  • Replace the quickstart with a working example that uses only the in-scope `AsobiWebSocket` API
  • Point engine/framework integrations (Phaser, Three.js, Pixi) at `examples/` rather than the bundled exports

Why

A README that overpromises is a credibility hole on Day 1 of any growth push. Honest scope reads as confident, not apologetic. Aligns with the architectural call that asobi-js is a protocol-only SDK; game-shape helpers belong in user code.

Test plan

  • README renders correctly on GitHub
  • Quickstart code matches `AsobiWebSocket` public API in `src/websocket.ts`
  • Follow-up PR will drop the deprecated typed REST modules

The previous README claimed full coverage of worlds, terrain, voting,
economy, leaderboards, social, tournaments, and storage as stable
features. The actual implementation is a thin WS+codec library with
scaffolded typed REST helpers, and the architectural direction is to
drop those helpers as the SDK narrows to a protocol-only transport.

Rewrite the README to:
- State the protocol-only scope explicitly
- Mark typed REST helpers as deprecated for v1.0
- Show a working WebSocket-based quickstart using only the in-scope API
- Point engine/framework integrations at examples/ rather than bundling

No code change. Code refactor follows in a separate PR.
@Taure Taure force-pushed the docs/scope-narrow-protocol-only branch from 621438c to 1e869dc Compare May 2, 2026 07:11
@Taure Taure merged commit 5fd5fb9 into main May 2, 2026
3 checks passed
@Taure Taure deleted the docs/scope-narrow-protocol-only branch May 2, 2026 07:12
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