Fork me on GitHub
#duct
<
2018-04-24
>
dadair03:04:47

Is there any way to enforce component startup order, without conflating configuration dependencies? e.g., say A must happen before B, but B doesn’t actually need to depend on A; just that the effects of A must happen before B. I know I can get this behaviour with a simple #ig/ref in component B’s options map, but not sure if there is another way