The "no" rule not expanded when used with a tag which is also a rule prefix

[Lalayqz]

====
TAGS
====
rule_prefix_tag = x1 x2
another_tag = y1 y2

=====
RULES     
=====
rule_prefix_tag [no thing:rule_prefix_tag:another_tag] -> []

In Pattern:Script, this rule correctly complies into:

[ no thing:x1:y1 no thing:x1:y2 ] -> [ ]
+ [ no thing:x2:y1 no thing:x2:y2 ] -> [ ]

But in PuzzleScript Next, this rule incorrectly complies into:

[ no thing:x1:y1 ] -> [ ]
+ [ no thing:x1:y2 ] -> [ ]
+ [ no thing:x2:y1 ] -> [ ]
+ [ no thing:x2:y2 ] -> [ ]

[Lalayqz]

Related: #38

[david-pfx]

Thanks. Do you have a repro case, or (better) can you suggest how to reproduce it in this test program?
http://localhost:8020/src/editor.html?demo=test/test_min_tags
Issue #38 was tested by line 210.

[Lalayqz]

Finally found it.. You mean this link.
In this case, this rule triggers the bug:
tag1 [no obj5:tag1:dirs] -> []

[david-pfx]

The cause seems to be that having a tag invokes a test for properties that have not been created.

Question: should every object name with 2 or more tags/mappings generate a hierarchy of property definitions?
PS Next has code to do exactly that, but which is never called!

[Lalayqz]

I think... I already fixed this issue in #152? My game runs excellently well after the fix.
The cause was just a typo in code.

[david-pfx]

Impressive! Yes, this fixes the bug. Thanks! Fixed (manually).