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
Description: Splitting a file into multiple files that import each other ends up breaking rule-s despite the project executing. It looks as if the different files are referring to the same types but to different node definitions, and hence the net never matches anything in order to start executing -- but it might be something else instead.
To reproduce: In the linked Gist, uncomment all the import lines and comment all the require lines. Despite everything parsing and executing, for some odd reason, rule-s won't match. I have not yet tried to debug the issue further, but I am going to guess that either the fact that I have "diamond" dependencies between files (A depends on B and C that both depend on D) manages to break the import system.
Description: Splitting a file into multiple files that
import
each other ends up breakingrule
-s despite the project executing. It looks as if the different files are referring to the same types but to differentnode
definitions, and hence the net never matches anything in order to start executing -- but it might be something else instead.To reproduce: In the linked Gist, uncomment all the
import
lines and comment all therequire
lines. Despite everything parsing and executing, for some odd reason,rule
-s won't match. I have not yet tried to debug the issue further, but I am going to guess that either the fact that I have "diamond" dependencies between files (A depends on B and C that both depend on D) manages to break the import system.Issue found while developing https://gist.github.com/bojidar-bg/6c52d1f1ed3fb3a583aaff9a184687fe
The text was updated successfully, but these errors were encountered: