Creating and destroying simulations as side effects of state changes was proving problematic and the code was slightly opaque.
Approach
Simplify things significantly by adding createSimulation and destroySimulation functions to the graphql context and call them from the resolvers in a more imperative manner.
Motivation
Creating and destroying simulations as side effects of state changes was proving problematic and the code was slightly opaque.
Approach
Simplify things significantly by adding
createSimulation
anddestroySimulation
functions to the graphql context and call them from the resolvers in a more imperative manner.