You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here we can see that parent scenario provides context for subscenario. Thus means subscenario can never know absolute state path and should rely only on relative state paths (e.g. do reactions.go("../../someState") instead of reactions.go("/someState")).
This opens a major issue for many StateNotFound runtime exceptions in bot.
What can be done:
Create new symbol in statepath resolution - ~, which will hold a root path of current scenario object. This will allow to use absolute paths from scenario root (from ~) and will give more flexibility for appended sub-scenarios.
So the transition will look like reactions.go(~/someState)
The text was updated successfully, but these errors were encountered:
After #139 was merged JAICF obtained ability to merge sub-scenarios inside parent scenario.
Scenario example:
Here we can see that parent scenario provides context for subscenario. Thus means subscenario can never know absolute state path and should rely only on relative state paths (e.g. do
reactions.go("../../someState")
instead ofreactions.go("/someState")
).This opens a major issue for many StateNotFound runtime exceptions in bot.
What can be done:
Create new symbol in statepath resolution -
~
, which will hold a root path of current scenario object. This will allow to use absolute paths from scenario root (from~
) and will give more flexibility for appended sub-scenarios.So the transition will look like
reactions.go(~/someState)
The text was updated successfully, but these errors were encountered: