Introducing Signals
2026-10-31
![]()
Ash Signals is aimed at side effects that turn into dependencies. When one action calls straight into another domain, the arrows soon run both ways and the code gets hard to change. With Signals, an action emits a signal, a module that defines the contract between them, and other domains listen for it, so every service depends on the signal's definition and none calls back into the action that raised it. Each side can then be tested and changed on its own. The documentation has the details.
Was this useful?