Skip to content

impact, path: a handler table keyed by an event type joins the publishers of that type [by key] - #1817

Merged
swapnilpaliwal-sd merged 1 commit into
apps/integration-0.1.9from
apps/javascript/event-type-join-across-services
Sep 30, 2026
Merged

swapnilpaliwal-sd merged 1 commit into
apps/integration-0.1.9from
apps/javascript/event-type-join-across-services

Conversation

@swapnilpaliwal-sd

Copy link
Copy Markdown
Contributor

A service publishes an event by its type (often through a constant: publish(TOPICS.CREATED, doc)), and another service dispatches it through a handler table keyed by the same string ({ [TOPICS.CREATED]: h }, { 'doc.created'(e) {} }, {"doc.created": h}). Before this change nothing joined the publisher to the handler.

  • ax_registration: handler-table entries are now registrations (kind table). A string constant resolves to its value. A key counts as written when it appears as a dotted literal or through a constant; the table's own key positions and the constant's declaration don't count.
  • impact.dl: impact of a publisher now lists each handler registered under its type [by key], and tests that publish the type reach the handler. Only production writers count against the key cap, and a handler that writes its own type is not counted as a writer.
  • path and the SQL port's key join read the same writes, so path now says "NOT independent" and names the table entry.
  • Cases: tests/cases/{javascript,python}/event-type-handler-table, with controls (a handler of another type, an arrow inside a data table, a test that publishes another type).

Checked: new cases went from 1/5 → 5/5 (JS) and 0/2 → 2/2 (Python). Product probes went from 47 → 48 of 70 (the Kafka cross-service delete probe now passes) with none regressed. By-key edges went from 0 → 247 over 14 keys, call_edges stayed at 8840, and indexing took 33.5s before and 32.1s after. Suite failures are the same set on the base in all five languages.

…hers of that type [by key]

A service publishes an event by its type string, often through a constant
(publish(TOPICS.CREATED, doc)); another holds a handler table keyed by the
same string ({ [TOPICS.CREATED]: onCreated }, { 'doc.created'(e) {} },
{"doc.created": on_created}) that a consumer dispatches by the message's
type. Nothing joined the two ends.

- ax_registration: table entries are registrations (kind table); string
  constants resolve to their value; a key written as a dotted literal or
  through a constant is a write, never the table's own key position or the
  constant's declaration.
- impact.dl: impact of a publisher lists each handler of its type [by key];
  tests that publish the type reach the handler. Only production writers
  count against the key cap, and a handler writing its own type is no writer.
- path and the SQL port's key join read the same writes.

Co-authored-by: axiomcode-bot[bot] <334110751+axiomcode-bot[bot]@users.noreply.github.com>
@swapnilpaliwal-sd
swapnilpaliwal-sd merged commit ea25723 into apps/integration-0.1.9 Sep 30, 2026
12 checks passed
@swapnilpaliwal-sd
swapnilpaliwal-sd deleted the apps/javascript/event-type-join-across-services branch September 30, 2026 08:50
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