Warning about infinite loops

[rowanseymour]

We allow these now, but maybe they still warrant some kind of visual warning to the user?

Have a ticket where the user inadvertently created a loop.

[nicpottier]

Just as a note I ran into this as well when playing with intents and was totally confused. I feel we should definitely show something to say why we aren't connecting here.

[rowanseymour]

Are we talking about two different things? You weren't able to make a loop but this user had inadvertently created a loop... in what case can't you create a loop?

[nicpottier]

Oh, it didn't connect for me, but no warning. Thought that was the issue.

…

On Tue, Oct 22, 2019, 8:05 AM Rowan Seymour ***@***.***> wrote: Are we talking about two different things? You weren't able to make a loop but this user had inadvertently created a loop... in what case can't you create a loop? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#651?email_source=notifications&email_token=AABJBAY6RQ3V55ZRSLXFIMLQP4JC3A5CNFSM4H3BB7PKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB6CQMA#issuecomment-545007664>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABJBAZ466R2QXNYLYK27ITQP4JC3ANCNFSM4H3BB7PA> .

[rowanseymour]

Ok from playing around.. you can't join an action to an action to the first action.. but you can if there's a split, even a passive one, in the loop... is that the rule? Seems like both cases might benefit from some visual explanation

[nicpottier]

I ran across this when having an intent split without a wait, so may not be as simple as any split.

[rowanseymour]

Seems like the rule could be that there needs to be a split, since any split provides a mechanism by which the loop could end.

i.e. just check the graph for closed loops