Validation stop firing when custom rule used together with another rule (don't know if just in the described context) about formkit HOT 4 CLOSED

This is fixed in 1.6.4 — thanks for the reproduction 💪

from formkit.

I was able to isolate this and reproduce it. It is a bug.

from formkit.

@justin-schroeder Somehow after this fix my validation stopped working:

1. I have a custom validator, that makes the field required when status is 1
2. when I click submit validator works. But when I change the status, it makes no difference, error stays
3. if I then change the status to unpublished, it works ONLY if I enter something in title and then delete (so it triggers the validation). Somehow status stopped working due to changes in listeners change in the commit.

There are 2 groups with same name, I know, but for a reason (some fields are translatable and get transformed into groups so we can switch and show/hide them). This works perfectly fine for months, form value and all that. Well, so did this rule until 1.6.4 was done.

Is there ANY way I get that node.at actually reacting to status field change? Note that when there are 2 languages there are 2 fields with name status, each in it's own group, that's why the call for $root.translations.en.
I'd do it without groups but sadly we cannot name elements like translations.es.title and make it work as object, so this was the only option.

Reproduction: https://formkit.link/eade881392843ffc606cf62a1af24bb4

from formkit.

Hey! Unfortunately that validation rule was only working due to a bug in prior versions that caused rules to run more often than they should. The only reason this doesnt currently work is that there are 2 groups with the same name. Here it is working fine when they are grouped:

https://formkit.link/8c4094cc5c88ba4f880123891f9d17f8

I understand the rational behind why you need that, however groups by the same names just wont work. Alternatively you could directly assign nodes to a group by using the parent prop.

from formkit.