Ryth Azhur
97237ed1a4
The TypeScript adapter produces the same manifest, the same X-Mizan-Invalidate headers, the same JSON invalidation protocol, and the same CDN-ready response headers as mizan-django. One Edge Worker. Two backend languages. Same protocol. Features: - @client decorator (function wrapper + class method decorator) - ReactContext class (same API as Django adapter) - Registry with context groups and param tracking - Context bundled GET: /api/mizan/ctx/<name>/ - Mutation POST: /api/mizan/call/ with server-driven invalidation - Three-tier auto-scoping (argument name matching → broad fallback) - Function-level affects targeting - private=True (rejected from RPC, in manifest for Edge) - X-Mizan-Invalidate header with URL-encoded params - Edge manifest generation (identical format to Django's) - render_strategy + user_scoped derivation 22 edge compatibility tests pass (Bun, 21ms): - Deterministic JSON, sorted keys - Cache-Control: public on GETs, no-store on mutations/errors - Vary: Authorization, Cookie - Header round-trip with special characters - Auto-scoped invalidation matches body and header - Function-level invalidation - Private function rejection - Manifest structure with PSR/dynamic_cached strategies Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
14 lines
495 B
TypeScript
14 lines
495 B
TypeScript
export { ReactContext } from './types'
|
|
export type { ClientOptions, EdgeManifest, RegistryEntry } from './types'
|
|
|
|
export { client } from './decorator'
|
|
|
|
export { register, getFunction, getAllFunctions, getContextGroups, clearRegistry } from './registry'
|
|
|
|
export { handleContextFetch, handleMutationCall } from './dispatch'
|
|
export type { MizanResponse } from './dispatch'
|
|
|
|
export { resolveInvalidation, formatInvalidateHeader } from './invalidation'
|
|
|
|
export { generateManifest } from './manifest'
|