mirror of
https://github.com/ash-project/ash.git
synced 2024-09-20 05:23:03 +12:00
James Harton
139058d4c0
Thanks to @carlgleisner for the [detailed reproduction](https://github.com/carlgleisner/reactor_notification_worker_issue). The problem was caused by an attempt to not have nested reactors indepdently publish their notifications separate to the parents but contained a logic flaw which caused the agent to not start, but only the first time you try and use a given reactor. The fix involves _always_ starting a notification agent for each reactor, but nesting them. When a reactor completes it either publishes it's notifications to the parent reactor or to ash if there are no parent reactors. |
||
|---|---|---|
| .. | ||
| action_test.exs | ||
| change_test.exs | ||
| create_test.exs | ||
| destroy_test.exs | ||
| notifications_test.exs | ||
| reactor_test.exs | ||
| read_one_test.exs | ||
| read_test.exs | ||
| tracing_test.exs | ||
| transaction_test.exs | ||
| update_test.exs | ||