Closed nnhjy closed 4 hours ago
Even if you do that, the unit__to_node will not be part of the model. Both unit and node will need to be active for that to happen.
In principle, we should de-activate that option, but it is way too complicated due to alternatives - one needs to track in which scenarios those units and nodes are both active in order to know when unit__to_node can be set to active. We could possibly signal scenarios where this conflict happens, but not any time soon, since there are more important things to do.
For example, now we can set (under the same alternative) an entity of
unit__to_node
with "active=true" with its correspondingunit
and/ornode
entity with "active=false".