Problem defining more than one action with the same transition path

I am trying to define two distinct actions that have the same transition path. Example:

State_A 'action_a' -> State_B;
State_A 'action_b' -> State_B;

I get an error like this: JssmError: already has "State_A" to "State_B" But it makes sense to have to different actions (as they may have two distinct state transition meaning) that define transition conditions.

[StoneCypher]

closing here because you’re chatting there

[StoneCypher]

I agree that this is a desirable thing

The reason I’m dragging my heels is that a huge portion of the codebase is written with the assumption that you can ask the machine for the edge between a and b, and get an unambiguous answer

To do this would break that, which is a massive breaking change and also would mean a whole bunch of stuff would need to move to being container based, which would probably slow things down by an order of ten

I have kicked around the idea of saying “it’ll return the main path and only main path has this restriction” but that still breaks older machines written without main paths

I’m still thinking over what I think is the right thing to do here

Would you be okay with my closing this, and talking on StoneCypher/fsl#325 instead, please? There are ~30 repos and it’s hard to keep track of things if they’re not all in the same place