Warning for loose ends inside weaves

[joningold]

The following source

=== knot 
    *   Option 

doesn't produce a loose end warning; meaning it's pretty easy to accidentally create a flow that dies at runtime. If the compiler could detect this, and warn, that would be epic.

[joethephish]

Ah yeah, I noticed that before but forgot to log it, that's definitely a biggie.

[KeineLimonade]

Only partially related to this issue, but I think someone should create a test suite for ink. This is a pretty simple file and it should not be possible to mess flow up that easily....

I could do this in spring break (in may). Maybe I will also implement this enhancement then.

[joethephish]

There’s already a test suite in the C# ink codebase. Just need to add this obvious case!

…

On 13 Mar 2018, 15:40 +0000, Juli ***@***.***>, wrote: Only partially related to this issue, but I think someone should create a test suite for ink. This is a pretty simple file and it should not be possible to mess flow up that easily.... I could do this in spring break (in may). Maybe I will also implement this enhancement then. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[ZephyrRaine]

After discussing this issue on Discord, we did an auto-tester that get all knots and stitches in the game, then plays them all and check if the story's state raise any error. It looks like these dead-ends do raise an error.

I don't know if that helps in any way but it's our workaround.

[joethephish]

Fixed in de744ae.