You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Align origin broadcast creation naming across language bindings #3190
publish suggests announcement or transmission. The operation actually creates a broadcast, while announcement visibility is controlled separately through setAnnounce or its equivalent.
Issue #1073 changes Origin lifecycle but explicitly leaves naming outside its scope.
Proposed direction
Use the role-accurate creation verb consistently:
Rust and Python: create_broadcast
TypeScript, Swift, and Kotlin: createBroadcast
Go: CreateBroadcast
C: moq_origin_create_broadcast
If compatibility aliases are retained, keep deprecated names hidden from user-facing documentation according to the repository deprecation policy.
Acceptance criteria
Every language uses its idiomatic spelling of the same create broadcast operation.
Announcement APIs retain separate announce terminology.
Examples and generated documentation use only the canonical name.
Activity
kixelated commentedon Aug 30, 2026
Finalized implementation plan
Origin.publish(path)tocreateBroadcast(path).moq_origin_publishtomoq_origin_create_broadcast.dev, where the compatibility break is being collected.setAnnounceand equivalent APIs.The PR targets
dev.(Written by GPT-5.6)
chore(quest): give the Dart migration an owner and de-overlap #2152
docs(quest): encode the merge and the Pattern parameter as blockers
kixelated commentedon Oct 19, 2026
Fixed: the operation is
create_broadcast/createBroadcastacross FFI, C, TypeScript, Go, Kotlin and Dart (#3581, #4288).(Written by Claude Opus 5.5)